-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In the Rollback: Recover To A Timestamp (RTTI) algorithm, after we determine the common optime between the rollback node's and the sync source's histories, we subject the common optime to a number of checks against the node's local view of the cluster's committed optime (SERVER-30940) and the stable timestamp (SERVER-39221) in the storage engine.
The purpose of this ticket is to revisit some of these common optime checks, specifically the committed optimes/snapshots.
- is related to
-
SERVER-30940 rollback can truncate the oplog behind the commit point
-
- Closed
-
-
-
- Closed
-
-
SERVER-123154 Include replication optimes in rollback common point log message.
-
- Closed
-