-
Bug
-
Resolution: Done
-
Major
-
9.0.0.Final
-
DataGrid Sprint #62, DataGrid Sprint #63, DataGrid Sprint #64
During node crash, two concurrent modifications in can both succeed in pessimistic tx cache.
This also causes random failures in InfinispanNodeFailureTest:
1. TX1 originating on A acquires lock for key X, A is primary owner
2. C is killed and B becomes primary owner of key X
3. TX2 originating on B acquires lock for key X, B is now primary owner
4. TX1 commits the tx, Prepare is sent with the new topology id so it commits fine
5. TX2 also commits the transaction
Log attached (this is not master but changes should not be related).
- duplicates
-
ISPN-5076 Pessimistic transactions can lose their locks when the primary owner changes
-
- Closed
-
-
ISPN-5307 Cache#remove(key) not behaving correctly under high load - while primary owner node is stopped
-
- Closed
-
- is cloned by
-
JDG-4438 Concurrent modifications succeed in pessimistic cache
-
- Closed
-
- is duplicated by
-
ISPN-7163 InfinispanNodeFailureTest.killedNodeDoesNotBreakReplaceCommand random failures
-
- Closed
-
- relates to
-
JDG-4385 org.infinispan.tx.InfinispanNodeFailureTest.tx.InfinispanNodeFailureTest fails randomly
-
- Closed
-