Details
-
Bug
-
Resolution: Fixed
-
None
-
None
-
*Location*: http://developer.couchbase.com/documentation/server/current/architecture/high-availability-replication-architecture.html
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36
*Screen Resolution*: 2560 x 1440
*Location*: http://developer.couchbase.com/documentation/server/current/architecture/high-availability-replication-architecture.html *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 *Screen Resolution*: 2560 x 1440
Description
In case of bi-directional XDCR where the same dataset exists on both the clusters, conflicts can arise
It is true that in any system using any XDCR topology (including just a simple unidirectional topology) that conflicts can occur when there are mutations occurring on both ends of the replication, not just in bi-directional topologies.
A more suitable summary of when conflicts could occur is as follows:
When the same dataset is being mutated on both ends of an XDCR replication (source and remote) then there is a high probability that conflicts will occur.