Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.7.0
Affects Version/s: None
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
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: Will Schultz
Reporter:: Will Schultz
Participants:: Githook User, Will Schultz
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Apr 29 2020 09:59:12 PM UTC
Updated:: Oct 29 2023 10:08:53 PM UTC
Resolved:: Jul 17 2020 04:02:37 PM UTC
Confidence Status Last Update:: 07/Jul/20 4:35 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates