-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
None
-
Storage Execution
-
Fully Compatible
Once MongoDB switches to journaling only the oplog, it will be necessary to ensure that the oplog is not truncated to a point in time that is after the last completed checkpoint.
MongoDB should track the timestamp for the last completed checkpoint, and ensure that oplog truncate doesn't remove any content newer than that point in time.
- depends on
-
SERVER-29891 Roll Back to Checkpoint: Call setStableTimestamp() when commit point or last applied changes
- Closed
- duplicates
-
SERVER-30460 Grow the oplog when the replication commit point falls behind the back of where it would normally be truncated to
- Closed