Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-38133

When asked to continue a transaction whose txnNumber is too new, TransactionParticipant must abort that transaction

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Replication
    • Sprint:
      Repl 2018-12-03, Repl 2018-12-17, Repl 2019-01-14

      Description

      When TransactionParticipant::_continueMutliDocumentTransaction() is called with a txnNumber that is higher than _activeTxnNumber, it returns NoSuchTransation but does not update _activeTxnNumber or abort the transaction. It must set _activeTxnNumber to txnNumber and abort the transaction (with the new txnNumber). This ensures that no future command may start a transaction with this txnNumber, so the commit decision for this txnNumber cannot change.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              tess.avitabile Tess Avitabile
              Reporter:
              tess.avitabile Tess Avitabile
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: