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

Check supportsRecoverToStableTimestamp before calling getLastStableCheckpointTimestamp

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

      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.vankeulen@mongodb.com Maria van Keulen
            Reporter:
            maria.vankeulen@mongodb.com Maria van Keulen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: