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/09/16 17:03:46 UTC
[jira] [Updated] (OAK-3411) Inconsistent read on DocumentNodeStore
startup
[ https://issues.apache.org/jira/browse/OAK-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger updated OAK-3411:
----------------------------------
Attachment: OAK-3411-test.patch
Attached a patch with tests to reproduce the regression.
> Inconsistent read on DocumentNodeStore startup
> ----------------------------------------------
>
> Key: OAK-3411
> URL: https://issues.apache.org/jira/browse/OAK-3411
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, mongomk
> Affects Versions: 1.0.20, 1.3.6, 1.2.5
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Blocker
> Fix For: 1.3.7, 1.2.6, 1.0.21
>
> Attachments: OAK-3411-test.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)