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

Investigate if magic restore can corrupt data due to oldest timestamp being greater than the stable timestamp

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • Repl 2024-03-04, Repl 2024-03-18, Repl 2024-04-01, Repl 2024-04-15

      In SERVER-84706, we determined a scenario where taking a stable checkpoint could corrupt data. In particular, this could occur during startup recovery for restore, when we tried to set the stable timestamp to a null value, which was a no-op. See doc for details.

      This ticket should investigate this scenario for magic restore, since we intend to do startup recovery in the process. We should outline why magic restore is safe in the face of this potential corruption.

            Assignee:
            ali.mir@mongodb.com Ali Mir
            Reporter:
            ali.mir@mongodb.com Ali Mir
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: