A failed unstashTransactionResources must leave transaction in stashed or aborted state

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • 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.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: