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

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.4.23, 1.6.15, 1.8.9
• Fix Version/s: 1.10.0, 1.2.31, 1.4.24, 1.8.10, 1.6.16, 1.9.13
• Component/s: rdbmk
• Epic Link: RDB Support
• Assignee: Julian Reschke
• Reporter: Julian Reschke
• Created: 03/Dec/18 15:18
• Updated: 07/May/20 12:10
• Resolved: 04/Dec/18 10:54

Description

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.

Issue Links

• relates to: OAK-7745 Clarify update semantics on deleted nodes