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

Roll Back to Checkpoint: Call setStableTimestamp() when commit point or last applied changes

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.5.12
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2017-07-31, Repl 2017-08-21
    • 0

      Every time a node advances its lastAppliedOpTime, the new optime will be added to a list of potential stable timestamps. The actual stable timestamp will be the greatest timestamp in this list that is less than or equal to the replication commit point. Timestamps can be removed from the list of ‘potential’ stable timestamps after it is less than the current stable timestamp. i.e. when it is less than the replication commit point and there is at least one other timestamp in the list greater than it that is also less than or equal to the replication commit point.

      Setting the 'stable' timestamp will tell WiredTiger what is a valid timestamp to take a checkpoint at.

            Assignee:
            william.schultz@mongodb.com William Schultz (Inactive)
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: