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

Command profiling should not use transaction read timestamp

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.0.0-rc0
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2018-05-07
    • 11

    Description

      When a transaction commits or aborts, it does not destroy the RecoveryUnit on the OperationContext. That RecoveryUnit still contains the _readAtTimestamp from the transaction. When we profile at the end of the command, we attempt to open the WT snapshot at time _readAtTimestamp. But since the transaction already committed/aborted, that snapshot can be destroyed, and we can get at SnapshotTooOld error. The RecoveryUnit for profiling should not have _readAtTimestamp set.

      Attachments

        Activity

          People

            matthew.russotto@mongodb.com Matthew Russotto
            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: