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

XMLWordPrintableJSON

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

      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.

              Assignee:
              Kaloian Manassiev
              Reporter:
              Tess Avitabile (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: