[SERVER-47845] Remove obsolete code related to storing and updating stable optime candidates - MongoDB Jira

XML

Word

Printable

Details

Type: Task
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 4.7.0
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2020-06-15, Repl 2020-06-29, Repl 2020-07-13, Repl 2020-07-27

Description

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.

Attachments

Issue Links

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

Activity

People

Assignee:: William Schultz (Inactive)

Reporter:: William Schultz (Inactive)

Participants:: Githook User, William Schultz

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: Apr 29 2020 09:59:12 PM UTC

Updated:: Mar 18 2021 04:46:53 PM UTC

Resolved:: Jul 17 2020 04:02:37 PM UTC