-
Bug
-
Resolution: Done
-
Blocker
-
8.1.0.Final
Similar to ISPN-6039, the test failure is caused by the state transfer put happening after the test's remove.
In this case, the command types are different, so blocking works correctly. However, when the ReadWriteKeyValueCommand executes before the state transfer put, it doesn't find any value, and it doesn't commit the entry. This means the key is not added to CommitManager's tracker map, and the state transfer put is allowed to write to it - effectively undoing the remove.
java.lang.AssertionError: expected:<null> but was:<v0>
at org.testng.AssertJUnit.fail(AssertJUnit.java:59)
at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364)
at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80)
at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:88)
at org.infinispan.distribution.rehash.NonTxBackupOwnerBecomingPrimaryOwnerTest.doTest(NonTxBackupOwnerBecomingPrimaryOwnerTest.java:194)
at org.infinispan.functional.distribution.rehash.FunctionalNonTxBackupOwnerBecomingPrimaryOwnerTest.testPrimaryOwnerChangingDuringRemove(FunctionalNonTxBackupOwnerBecomingPrimaryOwnerTest.java:103)
- is related to
-
-
- Closed
-
