Check supportsRecoverToStableTimestamp before calling getLastStableCheckpointTimestamp

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.1
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Storage NYC 2018-07-02
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The looping logic of oplog truncation was shortened as part of SERVER-34606 by checking whether it is safe to truncate the oplog earlier on in the nested loops than previously. supportsRecoverToStableTimestamp should be called prior to the getLastStableCheckpointTimestamp call that was added as part of SERVER-34606.

              Assignee:
              Maria van Keulen
              Reporter:
              Maria van Keulen
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: