[
https://issues.apache.org/jira/browse/OAK-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010950#comment-15010950
]
Marcel Reutegger commented on OAK-3646:
---------------------------------------
The issue happens when revisions of a change are purged from the
RevisionComparator and the order of two revisions changes. With the revision
comparator and delayed visibility of changes from other cluster nodes it
frequently happens that a local revision L happens before a foreign revision F
even though timestamp(F) < timestamp(L). The RevisionComparator maintains this
visibility information for revisions no older than one hour.
I think the only viable solution is to add this information to the
'readRevision' of a node state. Right now a node state is identified by a path
and a revision. In addition the key must also include the most recent visible
revision from other cluster nodes. This way the information of the
RevisionComparator is captured in the key and will survive the
RevisionComparator purge.
> Inconsistent read of hierarchy
> -------------------------------
>
> Key: OAK-3646
> URL: https://issues.apache.org/jira/browse/OAK-3646
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, documentmk
> Affects Versions: 1.0, 1.2
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Fix For: 1.4
>
>
> This is similar to OAK-3388, but about hierarchy information like which child
> nodes exist at a given revision of the parent node. This issue only occurs in
> a cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
