-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2018-04-09
-
55
Due to migration, killSession and other implicit transaction abort, multi-statement transaction functions need to consider the concurrency even if the session has been checked out.
If a high txnNumber is received from migration, the current transaction needs to abort. (SERVER-33432)
If migration has the same txnNumber, the current transaction must be in state None (retryable writes).
All accesses to the transaction functions must check the txnNumber and the state at the beginning.
- is duplicated by
-
SERVER-33368 Add snapshot read testing for txnNumber change on Session::onMigrateBeginOnPrimary() call
- Closed
- is related to
-
SERVER-33432 Implicit transaction abort
- Closed