-
Type: Task
-
Resolution: Fixed
-
Priority: Critical - P2
-
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).
- is related to
-
SERVER-86904 Conflict between initial sync setting the oldest timestamp and resharding pinning the oldest timestamp
- Closed