Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
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

In ~~SERVER-47844~~, we removed the usage of _chooseStableOpTimeFromCandidates, which contains the holdStableTimestampAtSpecificTimestamp failpoint. No tests that use the failpoint are currently failing yet, but we should add this failpoint back to ensure correct test behavior.

is caused by

SERVER-47844 Update _setStableTimestampForStorage to set the stable timestamp without using the stable optime candidates set when EMRC=true

Closed

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

Created:: Jul 13 2020 03:30:29 PM UTC
Updated:: Oct 29 2023 10:05:51 PM UTC
Resolved:: Jul 13 2020 04:07:57 PM UTC
Confidence Status Last Update:: 13/Jul/20 3:33 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates