First step here is that we need to add a js test for the behavior when replication majority commit point stops the oplog being truncated.
Depending on what that test turns up, there might be follow-on work to improve that behavior.
- is related to
-
TOOLS-1993 TOOLS qa-tests failing on server unstable
-
- Closed
-
-
-
- Closed
-
-
SERVER-29213 Have KVWiredTigerEngine implement StorageEngine::recoverToStableTimestamp
-
- Closed
-
- related to
-
SERVER-35747 Check supportsRecoverToStableTimestamp before calling getLastStableCheckpointTimestamp
-
- Closed
-