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

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • None
    • None
    • Replication
    • 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

          is related to

          Task - A task that needs to be done. SERVER-38134 Ensure config.transactions and TransactionParticipant have consistent state after every command

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-38135 Do not allow transactions on shard servers when the featureCompatibilityVersion is 4.0

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Task - A task that needs to be done. SERVER-38132 Aborting a transaction must always update config.transactions and write an abort oplog entry

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-38850 Perform noop write before returning NoSuchTransaction error

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              tess.avitabile@mongodb.com Tess Avitabile (Inactive)
              tess.avitabile@mongodb.com Tess Avitabile (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: