]
Galder Zamarreño updated ISPN-9919:
-----------------------------------
Status: Open (was: New)
Partial updates in Hibernate 2L cache upon failure
--------------------------------------------------
Key: ISPN-9919
URL:
https://issues.jboss.org/browse/ISPN-9919
Project: Infinispan
Issue Type: Bug
Components: Hibernate Cache
Affects Versions: 10.0.0.Alpha3, 9.4.6.Final
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Priority: Major
Fix For: 10.0.0.Final, 9.4.7.Final
This issue only affects 5.3:
For a repl read-write, entity cache, if the failure happens on the async FutureUpdate
call, that's fine because the Tombstone has already been sent and the cache won't
return anything.
If the failure happens when the Tombstone is sent, we seem to have a problem because it
results in stale data in the node that failed to apply the Tombstone. The FutureUpdate
that comes after the Tombstone cannot apply because it doesn't find the Tombstone.
In 5.3, Sync logs any errors but does not propagate it, so it ends up with inconsistent
state.