[
https://issues.apache.org/jira/browse/OAK-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707573#comment-16707573
]
Julian Reschke edited comment on OAK-7935 at 12/4/18 7:54 AM:
--------------------------------------------------------------
trunk: [r1848073|http://svn.apache.org/r1848073] (just the test which passes on
trunk)
1.8: [r1848096|http://svn.apache.org/r1848096]
1.6: [r1848127|http://svn.apache.org/r1848127]
was (Author: reschke):
trunk: [r1848073|http://svn.apache.org/r1848073] (just the test which passes on
trunk)
1.8: [r1848096|http://svn.apache.org/r1848096]
> RDB*Store: createOrUpdate may fail on stale cache when document was removed
> on different instance
> -------------------------------------------------------------------------------------------------
>
> Key: OAK-7935
> URL: https://issues.apache.org/jira/browse/OAK-7935
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: rdbmk
> Affects Versions: 1.6.15, 1.8.9
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Critical
> Labels: candidate_oak_1_4
> Fix For: 1.10, 1.8.10, 1.6.16, 1.9.13
>
>
> When executing `createOrUpdate()` on a node that is cached but has been
> removed from the database (by a different instance), the operation will fail,
> and continue to do so until the cache entry gets evicted or the cache gets
> manually cleared.
> The exception message somewhat misleadingly says "update of ... failed, race
> condition?"
> The problem has been fixed already in OAK-7725, but that change is rather big
> and non-trivial to backport.
> As a simpler fix for the maintenance branches we should invalidate the cache
> when the update fails, so that the system at least recovers and a retry will
> work.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
