[OAK-3903] Commit fails even though change made it to the DocumentStore

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0, 1.2
• Fix Version/s: 1.0.32, 1.2.17, 1.3.15, 1.4
• Component/s: core, documentmk
• Labels: resilience
• Epic Link: DocumentMK resilience
• Assignee: Marcel Reutegger
• Reporter: Marcel Reutegger
• Created: 21/Jan/16 08:54
• Updated: 12/Dec/17 14:06
• Resolved: 21/Jan/16 13:03

Description

In some rare cases it may happen that the DocumentNodeStore considers a commit as failed even though the changes were applied entirely to the DocumentStore. The issue happens when the update of the commit root is applied to the storage of a DocumentStore but then shortly after the communication between Oak the the storage system fails. On the Oak side the call will be considered as failed, but the change was actually applied.

The issue can be reproduced with the test attached to OAK-1641 and a replica-set with 3 nodes. Killing the primary node and restarting it a after a while in a loop will eventually lead to a commit that conflicts itself.

Issue Links

• is related to: OAK-7053 Commit fails even though change made it to the DocumentStore