-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2020-06-15, Repl 2020-06-29, Repl 2020-07-13, Repl 2020-07-27
Once we set the stable timestamp for storage without dependence on the stable optime candidates set, we can remove any obsolete/dead code related to storing and updating this set.
- depends on
-
SERVER-47844 Update _setStableTimestampForStorage to set the stable timestamp without using the stable optime candidates set when EMRC=true
- Closed
- is related to
-
SERVER-49732 Change _currentCommittedSnapshot to be an OpTime instead of OpTimeAndWallTime
- Closed
- related to
-
SERVER-55305 Retryable write may execute more than once if primary had transitioned through rollback to stable
- Closed