Details
-
Bug
-
Resolution: Not a Bug
-
Major
-
11.0.0.Final, 10.1.8.Final
-
None
Description
DistCacheWriterInterceptor uses skipSharedStores() for single-key write commands and multi-key functional commands in order to write to shared stores only on the primary owner of the key. For PutMapCommand it uses PersistenceManagerImpl.writeMapCommand(), which does not distinguish between shared and non-shared stores.
In addition to being inefficient, this makes it possible for a backup owner to update the value in the shared store after the primary owner released the lock, potentially out of order with another write operation (especially if the other write operation is single-key, so it only writes to the shared store from the primary).
Attachments
Issue Links
- is related to
-
ISPN-8196 Activation should occur at the primary node with shared stores
- New