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

Only update sessions with a transaction number

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 3.5.12
    • None
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2017-08-21

    Description

      There are a few places in op_observer_impl.cpp and oplog.cpp that call

      {set,get}

      LastWriteOptimeTs or saveTxnProgress if a session exists on the operation context, but they should instead check the operation context has a transaction number, because the session's state isn't loaded without one.

      SERVER-30281 adds invariants that _txnRecord has been set when some of these methods are called, so they will start to fail in the fuzzer.

      Attachments

        Activity

          People

            jack.mulrow@mongodb.com Jack Mulrow
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: