Commit timestamp queue getting out of order

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.6.3, 3.7.2, WT3.1.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage 2018-02-12
    • None

      The changes from WT-3854 have a bug in them where we're modifying a transaction's first_commit_timestamp value outside the lock and too early. That field is used in the queue cleanup code for comparison and so it must be set after that cleanup is complete, and while under the lock.

            Assignee:
            Susan LoVerso (Inactive)
            Reporter:
            Susan LoVerso (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: