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

Online rollbackToStableTimestamp

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.5.12, WT3.0.0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Storage 2017-07-10, Storage 2017-07-31, Storage 2017-08-21

      The recent history of changes in WiredTiger is represented by WT_UPDATE structures in the WiredTiger cache. As long as all updates after the stable timestamp are reachable, we could rollback to the stable timestamp by finding all of them and setting their txnid = WT_TXN_ABORTED. That makes those changes invisible to readers – i.e., it is equivalent to if the original transactions had rolled back instead of committing.

      and WT_PAGE_DELETED and the lookaside table. We have WT-3382 to address the former, and we should be able to read every page that is either in cache or needs a lookaside restore as part of the rollback operation.

            Assignee:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Reporter:
            michael.cahill@mongodb.com Michael Cahill (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: