[OAK-3411] Inconsistent read on DocumentNodeStore startup

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.3.6
• Fix Version/s: 1.0.21, 1.2.6, 1.3.7, 1.4
• Component/s: core, mongomk
• Assignee: Marcel Reutegger
• Reporter: Marcel Reutegger
• Created: 16/Sep/15 14:56
• Updated: 02/Mar/16 14:26
• Resolved: 17/Sep/15 07:23

Description

This is a regression introduced with OAK-2929. On DocumentNodeStore startup the RevisionComparator of the local instance is initialized with the current _lastRev entries from the other cluster nodes. The external _lastRev entries are 'seenAt' the same revision, which means for those revisions the RevisionComparator will use the clusterId to compare them. This is also described in OAK-3388.

OAK-2929 changed the sequence of revisions to check for conflicts from StableRevisionComparator to RevisionComparator. This makes the conflict check susceptible to the RevisionComparison behaviour described in OAK-3388. Commits may be rejected with a conflict, when there isn't really a conflict.

Issue Links

• relates to: OAK-3388 Inconsistent read in cluster with clock differences
• relates to: OAK-2929 Parent of unseen children must not be removable