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

[v7.0] Revert SERVER-86904

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Critical - P2 Critical - P2
    • 7.0.13
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • Repl 2024-08-19

      In 7.0, backporting SERVER-86904 changed how we advance the oldest timestamp during initial sync to use force=false rather than force=true. This ends up being a breaking change for initial sync workflows that don't wipe data on a node before putting it through initial sync.

      Using force=true is still safe because WT will not allow us to set timestamps in a dangerous way (where oldestTimestamp > stableTimestamp).

            Assignee:
            samy.lanka@mongodb.com Samyukta Lanka
            Reporter:
            samy.lanka@mongodb.com Samyukta Lanka
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: