Question regarding ‘Optimistic Replication’ introduced with v2.1 and Disaster recovery
We are not sure to understand ‘Optimistic Replication’ introduced with v2.1 and the optimal level we should set xdcrOptimisticReplicationThreshold when XDCR is used for disaster recovery only.
What we understand when XDCR is used for Disaster recovery only, is that there should be no conflicts resolution to loose on the destination, because destination is not accessed and updated by any app or any couchbase operation except XDCR.
Could you please confirm that when no create or update (set, incr, etc) are done on the XDCR destination cluster, xdcrOptimisticReplicationThreshold should be set really high (at a level matching the size of the biggest item in the bucket ), so that metadata are never read on the source cluster before putting the item in the replication queue ?
NOTE that this setting is cluster wide and effects all buckets.