Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
Fully Compatible
-
ALL
-
v4.0
-
Repl 2018-10-22, Repl 2018-11-05, Repl 2018-11-19
-
11
Description
If a transaction commits locally against a primary, but that primary goes down without replicating the commit, then if the commitTransaction command is retried against the new primary it will error with NoSuchTransaction. Generally a NoSuchTransaction error in this case indicates that the transaction either aborted or rolled back, and thus it would be safe to retry the entire transaction over. If, however, the writeConcern times out in this case then its possible that the original primary could be re-elected without rolling back the txn commit, and thus the transaction could wind up surviving after all.
Attachments
Issue Links
- causes
-
SERVER-37876 Unblacklist multi_statement_transaction_all_commands_same_session.js in concurrency_simultaneous_replication test suite
-
- Backlog
-
- has to be done before
-
-
- Closed
-
- is depended on by
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- is related to
-
SERVER-37181 commitTransaction command can attach TransientTransactionError label on more errors
-
- Closed
-
- related to
-
-
- Closed
-
-
-
- Closed
-