The looping logic of oplog truncation was shortened as part of SERVER-34606 by checking whether it is safe to truncate the oplog earlier on in the nested loops than previously. supportsRecoverToStableTimestamp should be called prior to the getLastStableCheckpointTimestamp call that was added as part of SERVER-34606.
- is related to
-
SERVER-34606 Test (and possibly fix) behavior around majority commit point and oplog truncation
-
- Closed
-