Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.6.7, 4.0.0-rc0
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v3.6
Sprint:
Repl 2018-05-21
Case:
Linked BF Score:
15
Confidence Status:
None
Work Order:
0

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

We set the stable timestamp using the "candidates" list which is populated whenever we move "lastApplied" forward. On primaries, we set lastApplied to the "all committed timestamp", which is not necessarily a timestamp in the oplog. On primaries we need to actually add the operation commit time to the candidates list, rather than the "all committed timestamp".

causes

SERVER-35113 Stable timestamp does not advance if lastApplied does not move forward, but all committed timestamp does, on single node RS

Closed

is related to

SERVER-33743 Use all_committed to set lastApplied on primary nodes

Closed

Assignee:: Judah Schvimer

Reporter:: Judah Schvimer

Participants:: Githook User, Judah Schvimer

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: May 08 2018 06:47:47 PM UTC

Updated:: Oct 29 2023 10:31:58 PM UTC

Resolved:: May 15 2018 07:16:14 PM UTC

Confidence Status Last Update:: 08/May/18 6:50 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates