Marcel Reutegger created OAK-3903:
-------------------------------------
Summary: Commit fails even though change made it to the
DocumentStore
Key: OAK-3903
URL: https://issues.apache.org/jira/browse/OAK-3903
Project: Jackrabbit Oak
Issue Type: Bug
Components: core, documentmk
Affects Versions: 1.2, 1.0
Reporter: Marcel Reutegger
Assignee: Marcel Reutegger
Fix For: 1.4
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
