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

Coordinate oplog truncate point with checkpoint timestamp

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Storage
    • None
    • Storage Execution
    • Fully Compatible

    Description

      Once MongoDB switches to journaling only the oplog, it will be necessary to ensure that the oplog is not truncated to a point in time that is after the last completed checkpoint.

      MongoDB should track the timestamp for the last completed checkpoint, and ensure that oplog truncate doesn't remove any content newer than that point in time.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: