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

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.7.9
• Fix Version/s: 1.7.14, 1.8.0
• Component/s: documentmk
• Assignee: Marcel Reutegger
• Reporter: Marcel Reutegger
• Created: 12/Dec/17 14:05
• Updated: 30/Dec/17 09:06
• Resolved: 13/Dec/17 07:19

Description

This is the same as OAK-3903, but for the new code path introduced with OAK-5788. The DocumentNodeStore will consider a commit as failed even though the changes were applied to the DocumentStore, but then the response fails e.g. because of a communication error or a crash of the MongoDB primary.

Issue Links

• relates to: OAK-3903 Commit fails even though change made it to the DocumentStore
• relates to: OAK-5788 Perform update of single node in one remote call if possible