Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
There is some bug in mvcc tx asynchronous rollback flow. Sometimes transaction is not rolled back completely: Remote transactions remain alive while Near and Dht transactions are terminated locally and on MVCC coordinator.
Reproducer: MvccTxRollbackAsyncTest#testMixedAsyncRollbackTypes
Attachments
Issue Links
- causes
-
IGNITE-10829 MVCC TX: Lazy query execution for query enlists.
- Resolved
- incorporates
-
IGNITE-10241 MVCC TX: orphaned remote transactions
- Resolved
-
IGNITE-10455 MVCC: Tx timeout can cause update counters inconsistency.
- Resolved
-
IGNITE-10583 MVCC: Assertion on txLog state update when recovering from WAL.
- Closed
- Is contained by
-
IGNITE-10518 MVCC: Update operation may hangs on backup on unstable topology.
- Resolved
-
IGNITE-10468 MVCC TX: Failover
- Resolved
- is duplicated by
-
IGNITE-10583 MVCC: Assertion on txLog state update when recovering from WAL.
- Closed
- relates to
-
IGNITE-7388 MVCC TX Support async tx rollback on timeout during version requesting.
- Resolved
-
IGNITE-10807 MVCC: Support long-running tx rollback on PME
- Resolved
- links to