Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-4057

round_to_oldest should establish txn snapshot after establishing rounded read timestamp

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.6.6, 4.0.0-rc0, WT3.1.0
    • None
    • None

    Description

      Currently, the round_to_oldest functionality observes the global oldest timestamp after the transaction's snapshot has already been generated. This is problematic because the oldest timestamp that is observed represents a different, later state of uncommitted transactions than what was captured by __wt_txn_get_snapshot(). This can cause an undesirable slicing between what is visible due to snapshot isolation and what is visible due to the read timestamp, if some transactions happen to commit in between getting the snapshot and rounding the read timestamp to the oldest timestamp.

      Attachments

        Issue Links

          Activity

            People

              michael.cahill@mongodb.com Michael Cahill
              milkie@mongodb.com Eric Milkie
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: