[IGNITE-10752] MVCC: Tests invariants are violated sometimes

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8
• Component/s: mvcc
• Labels: transactions
• Assignee: Igor Seliverstov
• Reporter: Roman Kondakov
• Created: 20/Dec/18 11:41
• Updated: 11/Mar/19 06:32
• Resolved: 21/Jan/19 12:27

Description

Sometimes tests are failed by violated invariants errors. For example, when total sum on accounts is not as expected.

Muted tests:

• CacheMvccPartitionedCoordinatorFailoverTest
  • testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence
  • testUpdate_N_Objects_SingleNode__PutGet_CoordinatorFails
  • testUpdate_N_Objects_ClientServer_Backups1_PutGet_CoordinatorFails_Persistence
  • testAccountsTxGet_SingleNode_CoordinatorFails
  • testAccountsTxGet_Server_Backups1_CoordinatorFails
  • testAccountsTxGet_ClientServer_Backups2_CoordinatorFails_Persistence
  • testAccountsTxScan_Server_Backups1_CoordinatorFails_Persistence
  • testAccountsTxScan_Server_Backups0_CoordinatorFails
  • testGetReadInProgressCoordinatorFails
  • testGetReadInsideTxInProgressCoordinatorFails_ReadDelay

• CacheMvccReplicatedCoordinatorFailoverTest
  • testAccountsTxGet_SingleNode_CoordinatorFails
  • testAccountsTxGet_Server_Backups0_CoordinatorFails_Persistence
  • testUpdate_N_Objects_SingleNode__PutGet_CoordinatorFails

• CacheMvccTransactionsTest.testMvccCoordinatorChangeSimple
• DataStreamProcessorMvccPersistenceSelfTest.testTryFlush
• IgniteCacheGroupsTest.testCreateDestroyCachesMvccTxReplicated
• CacheMvccReplicatedSqlCoordinatorFailoverTest.testUpdate_N_Objects_ClientServer_Backups0_Sql_Persistence
• CacheMvccPartitionedSqlCoordinatorFailoverTest
  • testUpdate_N_Objects_ClientServer_Backups2_Sql
  • testUpdate_N_Objects_ClientServer_Backups1_Sql_Persistence
  • testUpdate_N_Objects_SingleNode_Sql_Persistence
  • testUpdate_N_Objects_ClientServer_Backups0_Sql_Persistence
  • testPutAllGetAll_ClientServer_Backups1_SinglePartition_RestartRandomSrv_SqlDml
  • testPutAllGetAll_Server_Backups1_SinglePartition_RestartRandomSrv_SqlDml
  • testPutAllGetAll_ClientServer_Backups3_RestartCoordinator_ScanDml
  • testAccountsTxSql_Server_Backups0_CoordinatorFails
  • testAccountsTxSql_Server_Backups1_CoordinatorFails_Persistence

junit.framework.AssertionFailedError: Unexpected error: junit.framework.AssertionFailedError: expected:<0> but was:<4>
	at junit.framework.Assert.fail(Assert.java:57)
	at junit.framework.TestCase.fail(TestCase.java:227)
	at org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1362)
	at org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1350)
	at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)

Issue Links

• contains: IGNITE-10537 MVCC: Client reconnect tests became unstable after mvcc coordinator reassign fix.
• is duplicated by: IGNITE-10750 MVCC: Unexpected tx state exception in multithreaded tests
• is related to: IGNITE-10518 MVCC: Update operation may hangs on backup on unstable topology.
• is related to: IGNITE-9428 MVCC TX: MvccQueryTrackerImpl.onDone() semantic is broken.
• is related to: IGNITE-10185 TX can hang forever if any runtime exception occurs on txFinish.
• is related to: IGNITE-10219 MVCC: TX: Backup node update may fail after lost tx rollback.
• is related to: IGNITE-10378 MVCC TX: Possible race on MVCC coordinator reassignment
• links to: GitHub Pull Request #5809