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

Aborting in-progress transactions on step-up should clear session state before returning

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.4.0-rc10, 4.2.9, 4.7.0
    • Replication
    • None
    • Fully Compatible
    • ALL
    • v4.4, v4.2
    • Repl 2020-06-15
    • 11

    Description

      Step-up can run further operations on the same operation context, which will be left with session metadata (lsid, txnNumber, etc.) from the last transaction the node aborted as part of step-up.

      These operations can then invariant that the session is not checked out even though they have session metadata on their operation context. Ordinarily they would exit early for not having a stmtId here. That stmtId is assigned here from the update request, which comes from here. That would return an uninitialized stmtId, except the txnNumber is not null like it should be here.

      Attachments

        Issue Links

          causes

          Task - A task that needs to be done. SERVER-48729 Don't duplicate maxNumberOfTransactionOperationsInSingleOplogEntry parameter in refine_collection_shard_key_abort_on_stepup.js

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-48600 RefineCollectionShardKey does not check for transaction write concern errors

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-49459 Check sticky state on OperationContext and consider fixing

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

          Activity

            People

              judah.schvimer@mongodb.com Judah Schvimer
              judah.schvimer@mongodb.com Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: