-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Repl 2019-06-17, Repl 2019-07-01, Repl 2019-07-15, Repl 2019-07-29
There is a one-to-one mapping between the txnNumber and a transaction participant / retryable write (no transaction). We should make a participant only know of its constant transaction number. Bumping txnNumber will try to abort the current participant, which throws an exception if it can't, and start a new one. As a result, participant only needs to check its state (aborted or not) and should never know of the change of the transaction number.
- related to
-
SERVER-37681 Make it clear from the stack trace whether a command is running in a checked out session
- Closed