Couchbase 3.0 XDCR not replication with some keys (after network failure)

Couchbase Server
1

I have XDCR with 2 clusters with bi-directional replication(one cluster running Couchbase 3.0, another running Couchbase 2.5). After a network failure (40% timeout connections between 2 cluters), some keys are not able to replication.
I tried to change, delete documents at both clusters but nothing happened.
I found out one key has different CAS value in each cluster.

Does anyone know any workaround? Thanks in advance.

2

Hi @cuongdd2, this is not supposed to happen. do you see percent complete under the stats for outbound XDCR operations on both sides?

3

Also you can enable XDCR Trace to log all the activities. Here is how you can do that -

either edit corresponding line in static_config to “{loglevel_xdcr_trace, debug}.” and restart the server or post “ale:set_loglevel(xdcr_trace, debug).” to /diag/eval.