-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Sharding
-
Fully Compatible
-
ALL
-
Sharding 2018-10-08, Sharding 2018-10-22
-
21
If a transaction with a higher txnNumber is started, but it fails validation and uasserts in TransactionParticipant::beginOrContinue() prior to aborting the previous transaction, then the txnNumber on the Session will be the new value, but there will still be an in-progress transaction in TransactionParticipant. The in-progress transaction is no longer accessible, since the txnNumber on Session has been bumped, so a client cannot abort it. We should never bump the txnNumber on Session without aborting the previous transaction.
- depends on
-
SERVER-36799 Move transaction related functionality from Session into TransactionParticipant
- Closed
- related to
-
SERVER-36847 Procedure to abort in-progress transactions in snapshot_read_utils.js no longer works
- Closed