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

Check supportsRecoverToStableTimestamp before calling getLastStableCheckpointTimestamp

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.1
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Storage NYC 2018-07-02
    • Linked BF Score:
      0

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: