Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
None
-
Replication
-
ALL
Description
If TransactionParticipant::Participant::unstashTransactionResources fails nonfatally for any reason, it must either leave the transaction in a stashed state or an aborted state, otherwise the transaction resources may be lost. In service_entry_point_common, unstashTransactionResources has no guard around it, and it's not clear what such a guard could do because a failure from unstashTransactionResources currently may leave the transaction either stashed or unstashed.
Attachments
Issue Links
- duplicates
-
SERVER-42388 Release the transaction lock resources and abort storage transaction for unprepared transactions on failure to unstash the transaction resources to opCtx.
-
- Closed
-
- is related to
-
SERVER-41556 Must handle failure to reacquire locks and ticket when unstashing transaction
-
- Closed
-