[
https://issues.apache.org/jira/browse/OAK-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902666#comment-14902666
]
Marcel Reutegger edited comment on OAK-3433 at 9/22/15 1:59 PM:
----------------------------------------------------------------
Initially my suspicion was that the conflict detection does not work in some
edge case like a background read between a rebase and the commit of the
changes. However, it turns out there is another problem introduced by OAK-2829.
The cache invalidation based on journal entries does not work reliably. The
issue occurs when a background read picks up changes from another cluster node,
before the background update pushes local changes to a journal entry. The id of
the journal entry is derived from the current head revision instead of the most
recent _lastRev entry. This means, later a background read on another cluster
node will not have its caches invalided properly.
was (Author: mreutegg):
Initially my suspicion was that the conflict detection does not work in some
edge case like a background read between a rebase and the commit of the
changes. However, it turns out there is a more another problem introduced by
OAK-2829.
The cache invalidation based on journal entries does not work reliably. The
issue occurs when a background read picks up changes from another cluster node,
before the background update pushes local changes to a journal entry. The id of
the journal entry is derived from the current head revision instead of the most
recent _lastRev entry. This means, later a background read on another cluster
node will not have its caches invalided properly.
> Commit does not detect conflict when background read happens after rebase
> -------------------------------------------------------------------------
>
> Key: OAK-3433
> URL: https://issues.apache.org/jira/browse/OAK-3433
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, mongomk
> Affects Versions: 1.2.3, 1.3.2, 1.0.19
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Critical
> Labels: resilience
> Fix For: 1.3.7, 1.2.7, 1.0.22
>
>
> The conflict check does not consider changes that are made visible between
> the rebase and the background read.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
