Details
-
Bug
-
Resolution: Fixed
-
Blocker
-
6.6.3, 7.0.2
-
7.0.2-6683
-
Untriaged
-
Centos 64-bit
-
1
-
No
Description
Build: 7.0.2-6683
Steps to reproduce:
- Create a doc using Sync_Write (MAJORITY)
- Delete the same doc using non-sync delete operation
- Create the same same using sync_write (MAJORITY)
Observation:
Rev Id of the document after step#3 remains 2 instead of '3'
Impact
Revision id (revid) is primarily used for XDCR conflict resolution. Documents which are affected by this issue may not have the correct update selected if the same key exists on an XDCR target Bucket.
Ref: MB-48179
Attachments
Issue Links
- relates to
-
MB-48179 SyncDeletes do not update maxDelRevSeqno, which can cause rev ids to go backwards
- Closed