-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
5.2.0.Final
-
None
The test does 2 sequential put operations from different nodes (1st put from node A, 2nd put from node B) and then checks that the last put value appears in both nodes.
However, the cache is configured with async commit phase, so the 1st tx's commit command can be executed on node B after the 2nd tx was already committed there:
00:32:01,165 TRACE (testng-VersionedConditionalOperationsTest:___defaultcache) [EntryWrappingInterceptor] About to commit entry ClusteredRepeatableReadEntry(66b3cb0){key=key_1, value=value_1, oldValue=null, isCreated=true, isChanged=true, isRemoved=false, isValid=true}
00:32:01,191 TRACE (testng-VersionedConditionalOperationsTest:___defaultcache) [EntryWrappingInterceptor] About to commit entry ClusteredRepeatableReadEntry(1af81e1){key=key_1, value=value_2, oldValue=null, isCreated=true, isChanged=true, isRemoved=false, isValid=true}
00:32:01,188 TRACE (OOB-1,ISPN,NodeB-21498:___defaultcache) [EntryWrappingInterceptor] About to commit entry ClusteredRepeatableReadEntry(7e2a710c){key=key_1, value=value_1, oldValue=null, isCreated=true, isChanged=true, isRemoved=false, isValid=true}
00:32:01,198 TRACE (OOB-2,ISPN,NodeA-27406:___defaultcache) [EntryWrappingInterceptor] About to commit entry ClusteredRepeatableReadEntry(61c63eff){key=key_1, value=value_2, oldValue=value_1, isCreated=false, isChanged=true, isRemoved=false, isValid=true}
The test should either use sync commit, or it should avoid checking consistency after a scenario like this.
- duplicates
-
-
- Closed
-
