-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2020-05-18, Repl 2020-06-01, Repl 2020-06-15, Repl 2020-06-29, Repl 2020-07-13
-
15
Currently, we update the stable timestamp inside ReplicationCoordinatorImpl::_setStableTimestampForStorage by computing the stable optime from the set of stable optime candidates. We should remove the dependence on the stable optime candidates for setting the stable timestamp and updating the committed snapshot when enableMajorityReadConcern:true. We should be able to set the stable timestamp for storage directly as min(all_durable, lastCommittedOpTime). We will not remove any of the logic for computing and updating the stable optime candidates set as a part of this ticket.
- causes
-
SERVER-49472 Add back holdStableTimestampAtSpecificTimestamp failpoint that was removed from runnable code path
- Closed
- depends on
-
SERVER-49006 Only advance oldest timestamp when setting lastApplied during initial sync instead of STARTUP2 state
- Closed
- is depended on by
-
SERVER-48518 Rollback via refetch (EMRC = false) can make readers to see the rolled back data even after the rollback node catches up to primary.
- Closed
-
SERVER-47845 Remove obsolete code related to storing and updating stable optime candidates
- Closed
- is related to
-
SERVER-33806 Oldest timestamp can move ahead of the commit point.
- Closed
-
SERVER-30577 Clear list of stable timestamp candidates on Rollback and Initial Sync
- Closed
-
SERVER-33292 Have storage dictate where replication recovery should begin playing oplog from
- Closed
-
SERVER-49167 Update _setStableTimestampForStorage to set the stable timestamp without using the stable optime candidates set when EMRC=false
- Closed
- related to
-
SERVER-55305 Retryable write may execute more than once if primary had transitioned through rollback to stable
- Closed
-
SERVER-49221 Complete TODO listed in SERVER-47844
- Closed
-
SERVER-49355 Complete TODO listed in SERVER-47844
- Closed
-
SERVER-49406 Complete TODO listed in SERVER-47844
- Closed