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

Recipient clears lastCommittedOpTime and currentCommittedSnapshot after applying recipient config

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Server Serverless 2022-09-05
    • 165

    Description

      We originally decided to set the lastCommittedOpTime to blockOpTime when applying the recipient config, but later realized that it would be possible for that value to be different (and more important earlier) than the currentCommittedSnapshot (which is a fact propagated through WiredTiger). There is no precedent for these values moving backwards, but there is precedent for clearing these values since that simulates the environment during startup recovery, and in certain reconfig scenarios. Instead, we will clear both values when applying the recipient config.

      Attachments

        Activity

          People

            matt.broadstone@mongodb.com Matt Broadstone
            matt.broadstone@mongodb.com Matt Broadstone
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: