You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2018/12/03 15:19:00 UTC

[jira] [Created] (OAK-7935) RDB*Store: createOrUpdate may fail on stale cache

Julian Reschke created OAK-7935:
-----------------------------------

             Summary: RDB*Store: createOrUpdate may fail on stale cache
                 Key: OAK-7935
                 URL: https://issues.apache.org/jira/browse/OAK-7935
             Project: Jackrabbit Oak
          Issue Type: Technical task
          Components: rdbmk
    Affects Versions: 1.8.9, 1.6.15
            Reporter: Julian Reschke
            Assignee: Julian Reschke


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)