You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2015/03/17 13:59:38 UTC

[jira] [Created] (OAK-2642) DocumentNodeStore.dispose() may leave repository in an inconsistent state

Marcel Reutegger created OAK-2642:
-------------------------------------

             Summary: DocumentNodeStore.dispose() may leave repository in an inconsistent state
                 Key: OAK-2642
                 URL: https://issues.apache.org/jira/browse/OAK-2642
             Project: Jackrabbit Oak
          Issue Type: Bug
          Components: core, mongomk
    Affects Versions: 1.0
            Reporter: Marcel Reutegger
            Assignee: Marcel Reutegger
            Priority: Critical
             Fix For: 1.1.8


The repository may become inconsistent when a commit happens while the DocumentNodeStore is disposed. 

The node store writes back pending _lastRevs and then unset the active flag in the clusterNodes collection. It is possible a commit gets through even after the _lastRevs had been updated and the active flag is cleared. This means the missing _lastRev updates will not be recovered on a restart or by another cluster node.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)