Details
Description
Note this is fixed upstream (3.0/master).
Identified that any restart with an access.log pushes the code down a path which creates "Item" objects with a sequence number of 1.
This is due to the constructor not being given the seq number and it defaulting to 1.
This happens when there's a server restart, e.g. offline upgrade or just a node reboot. The effect of this problem on XDCR is not pretty (likely to lose mutations in XDCR target).
If the user performs online/swap-rebalance and always swaps out crashed nodes and rebalances back, i.e. nodes always get their data from partner node/replicas, they're probably ok...
Raising this as an MB even though it's fixed upstream as I'm speculating that we'd like to track the back-port of this fix into 2.5.2 or a HOTFIX.
Patch to be uploaded shortly.