Description
- Setup 2 node local source cluster with 6.0.0-1673
- node 1: 192.168.56.101
- node 2: 192.168.56.102
- Setup 2 node EC2 destination cluster with 6.0.0-1673
- node1: ec2-34-216-196-148.us-west-2.compute.amazonaws.com (private IP : 172.31.2.94)
- node2: ec2-54-213-203-196.us-west-2.compute.amazonaws.com (private IP: 172.31.43.25)
- While rebalance is still pending after adding node2 on EC2 cluster, create replication from "mem" bucket on src(C1) to "rep-mem" on dest(C2) specifying public DNS (ec2-34-216-196-148.us-west-2.compute.amazonaws.com) for destination. Load bucket with 50K docs.
- Do rebalance on the EC2 cluster. Node2 added successfully.
- Mutations remain in source outbound queue forever.
This error is seen in the logs:
<code>
2018-10-01T16:10:37.299-07:00 ERRO GOXDCR.RemClusterSvc: Failed to refresh remote cluster reference remoteCluster/jrcZeER8pUuJo-qacR8J0YD3HClabsER-hwJbMpmzg0= since none of the nodes in target node list is accessible. node list = [172.31.2.94:8091]
2018-10-01T16:10:37.299-07:00 WARN GOXDCR.RemClusterSvc: Error occured while doing refresh during getting remote cluster reference for 56588e1ffae793e05948c77a6e28360d: Failed to refresh remote cluster reference remoteCluster/jrcZeER8pUuJo-qacR8J0YD3HClabsER-hwJbMpmzg0= since none of the nodes in target node list is accessible. node list = [172.31.2.94:8091]
</code>