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

WT_SESSION.checkpoint: read timestamp 6373c older than oldest timestamp

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.5.12, WT3.0.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage 2017-09-11

      If an application is using the stable_timestamp API correctly, then it should always be the case that oldest_timestamp <= stable_timestamp. However, a checkpoint first reads stable_timestamp and (sometime later) starts a transaction. During that interval, the oldest_timestamp could move forward, leading to this error.

      That appears to have happened in testing:

      http://build.wiredtiger.com:8080/job/wiredtiger-test-recovery-stress/510/console

      Checkpoint needs to prevent the oldest_timestamp moving forward until its transaction has started.

            Assignee:
            michael.cahill@mongodb.com Michael Cahill (Inactive)
            Reporter:
            michael.cahill@mongodb.com Michael Cahill (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: