Weird revision for new documents in CB 5

[drigby]

@greengreengreen

However this behaviour would be OK if the replicated documents had the same revision.

But they don’t, they always have revision 1. Then if you edit the replicated doc, it’s revision becomes 2, which is lower than original doc revision so XDCR does not replicate it. Then we have a stale doc on the other server.

Unless I pause XDCR then create a doc, it gets revision 13 for example, then resume XDCR the replicated doc also has revision 13. Then editing the doc on either server bumps the revision to 14 on both.

So our issue is that when XDCR is active it incorrectly replicates the revision for a new doc.

Thanks for clarifying.

I can’t explain what you’re seeing - that doesn’t sound expected. What XDCR conflict resolution mode (revID/ time-based) are you using?

You might want to raise an issue on XDCR at http://issues.couchbase.com if you believe you have a regression since 4.x.