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

Unused parameter "stableTimestampForRecovery"

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor - P4 Minor - P4
    • 4.3.1
    • None
    • Replication
    • None
    • Fully Compatible
    • Repl 2019-08-26

    Description

      This value is in OplogApplier::Options and it's a parameter to SyncTail::syncApply and all the lambdas in kOpsMap. According to the comment in OplogApplier, "For replication recovery only. During replication rollback, this is used to keep track of the stable timestamp from which we replay the oplog." After the Oplog Durability project, however, this parameter is unused.

      As pavithra.vetriselvan says, "This is no longer needed after the oplog durability project because we do not need to compare the commitTimestamp to the stableTimestamp. This was originally used to tell whether prepared operations were already reflected in the data."

      Attachments

        Activity

          People

            jesse@mongodb.com A. Jesse Jiryu Davis
            jesse@mongodb.com A. Jesse Jiryu Davis
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: