-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
Replication
There's no guarantee that the stable timestamp aligns with a timestamp from an oplog entry. This can happen on the primary when the `allDurable` is used to calculate the stable timestamp, since this value is the timestamp of the latest open oplog hole minus 1. We should test magic restore with a backup that explicitly has a stable timestamp derived from this `allDurable` point and sure our invariants about timestamps hold.
- is duplicated by
-
SERVER-86650 Add magic restore test to ensure oplog truncation removes oplog holes
- Closed