[
https://issues.apache.org/jira/browse/OAK-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904491#comment-14904491
]
Marcel Reutegger edited comment on OAK-3388 at 9/23/15 1:21 PM:
----------------------------------------------------------------
Attached work-in-progress patch.
These changes also resolve OAK-2929.
Most notable changes are:
- RevisionComparator compares based on revision time when two external
revisions with the same seenAt range are compared.
- Background read in DocumentNodeStore delays the operation when it detects
that clocks are not in sync. This ensures revision comparison for visible
changes is stable and does not change when seenAt ranges older than one hour
are purged.
- Clarified NodeDocument.getNewestRevision()
Feedback welcome.
was (Author: mreutegg):
Attached work-in-progress patch.
These changes also resolve OAK-2929.
Most notable changes are:
- RevisionComparator compares based on revision time when two external
revisions with the same seenAt range are compared.
- Background read in DocumentNodeStore delays the operation when it detects
that clocks are not in sync.
- Clarified NodeDocument.getNewestRevision()
Feedback welcome.
> Inconsistent read in cluster with clock differences
> ---------------------------------------------------
>
> Key: OAK-3388
> URL: https://issues.apache.org/jira/browse/OAK-3388
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, mongomk
> Affects Versions: 1.0, 1.2
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Labels: resilience
> Fix For: 1.3.7
>
> Attachments: OAK-3388.patch
>
>
> This issue is similar to OAK-2929 but related to how the DocumentNodeStore
> reads a node state when there is a clock difference between multiple cluster
> nodes. The node state read from a NodeDocument may not be correct when there
> is a clock difference.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
