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

Bumping txnNumber on Session must always abort running transaction with lower txnNumber

    XMLWordPrintable

Details

    • Fully Compatible
    • ALL
    • Sharding 2018-10-08, Sharding 2018-10-22
    • 21

    Description

      If a transaction with a higher txnNumber is started, but it fails validation and uasserts in TransactionParticipant::beginOrContinue() prior to aborting the previous transaction, then the txnNumber on the Session will be the new value, but there will still be an in-progress transaction in TransactionParticipant. The in-progress transaction is no longer accessible, since the txnNumber on Session has been bumped, so a client cannot abort it. We should never bump the txnNumber on Session without aborting the previous transaction.

      Attachments

        Issue Links

          Activity

            People

              kaloian.manassiev@mongodb.com Kaloian Manassiev
              tess.avitabile@mongodb.com Tess Avitabile (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: