-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Replication
-
Fully Compatible
-
ALL
-
Repl 2024-03-04, Repl 2024-03-18
This came out of an investigation during SERVER-84706. Today, startup recovery for restore first sets the initial data timestamp to the sentinel so that we take unstable checkpoints. We also attempts to set the stable timestamp to Timestamp::min(). However, this is essentially a no-op, as we do not allow trying to reset the stable timestamp if it is null. In addition, it is not safe to set the stable timestamp backwards.
After discussion within RSS, we determined that it should be equally performant and safe to set the stable timestamp during startup recovery for restore and take stable checkpoints (SERVER-87919). This would allow us to advance the stable timestamp alongside the oldest timestamp, preventing any future occurrences of SERVER-84706. We should do this to resolve this bug.
- is depended on by
-
SERVER-82686 Investigate if we need to explicitly take a stable checkpoint at the end of magic restore
-
- Closed
-
- is related to
-
-
- Closed
-
-
SERVER-87919 Stop taking unstable checkpoints during recovery for restore
-
- Open
-
- related to
-
-
- Closed
-
-
-
- Closed
-