Details
Description
I have loaded 4047 and duplicated the problem.
I can replicate encrypted from Cluster 1 to Cluster2. NYC-bucket to London-bucket
I CANNOT replicate encrypted from Cluster2 to Cluster1. London-bucket to NYC-bucket.
I have set up cluster references between the two using certificates in the GUI.
(I suspected that on initiation both clusters may have generated the same Self-signed SSL certificate, since it did not work)
I then changed the certificates by having each cluster regenerate a new certificate. This also did not work and I continue to have one way replication functioning where bi-directional encrypted should be functioning.
my nodes are as follows LoginID = Administrator password = couchbase
NYC-Cluster
ec2-52-6-187-106.compute-1.amazonaws.com ChrisCluster_1
ec2-52-6-88-13.compute-1.amazonaws.com ChrisCluster_2
ec2-52-6-83-21.compute-1.amazonaws.com ChrisCluster_3
ec2-52-6-86-154.compute-1.amazonaws.com ChrisCluster_4
ec2-52-5-231-238.compute-1.amazonaws.com ChrisCluster_5
ec2-52-6-94-204.compute-1.amazonaws.com ChrisCluster_6
London-Cluster
ec2-54-84-87-106.compute-1.amazonaws.com SecondCluste_1
ec2-54-86-134-21.compute-1.amazonaws.com SecondCluste_2
ec2-52-4-2-240.compute-1.amazonaws.com SecondCluste_3
ec2-52-7-140-134.compute-1.amazonaws.com SecondCluste_4
Attachments
For Gerrit Dashboard: MB-16204 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
55140,5 | MB-16204 fix issue with ssl port parsing | master | goxdcr | Status: MERGED | +2 | +1 |
55445,2 | MB-16204 fix issue with ssl port parsing | sherlock | goxdcr | Status: MERGED | +2 | +1 |
56523,4 | MB-16204 fix incorrect hostname in ssl port computation | master | goxdcr | Status: MERGED | +2 | +1 |
56645,2 | MB-16204 fix incorrect hostname in ssl port computation | sherlock | goxdcr | Status: MERGED | +2 | +1 |