[jira] [Updated] (OAK-7935) RDB*Store: createOrUpdate may fail on stale cache when document was removed on different instance

["Julian Reschke (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OAK-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Reschke updated OAK-7935:
--------------------------------
    Summary: RDB*Store: createOrUpdate may fail on stale cache when document was removed on different instance  (was: RDB*Store: createOrUpdate may fail on stale cache)

> 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
>
> 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)