Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Replication
Labels:
None

Assigned Teams:

Replication
Operating System:
ALL
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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.

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

Assignee:: [DO NOT USE] Backlog - Replication Team
Reporter:: Matthew Russotto
Participants:: [DO NOT USE] Backlog - Replication Team, Judah Schvimer, Matthew Russotto, Siyuan Zhou, Suganthi Mani
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Jul 24 2019 05:54:32 PM UTC
Updated:: Dec 06 2022 02:52:50 AM UTC
Resolved:: Jul 24 2019 07:47:14 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates