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

Add --oplogMinRetentionHours argument and use it to limit oplog truncation

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.3.4
    • Replication, Storage
    • None
    • Fully Compatible
    • Execution Team 2020-02-10, Execution Team 2020-02-24
    • 0

    Description

      Allow specifying a minimum retention time for the oplog in addition to a maximum size. Oplog entries are only deleted if they both exceed the size cap and the minimum retention time.

      The retention time is specified in hours, allowing fractions. The default is 0 hours (feature is off).

      Use the ReplicationCoordinator::getLastAppliedOpTime() as proxy for "now" and the timestamp derived from Stone::lastRecord as the most recent timestamp in the next oplog range to truncate.

      Attachments

        Issue Links

          Activity

            People

              andrew.chen@mongodb.com Andrew Chen
              geert.bosch@mongodb.com Geert Bosch
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: