-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v3.6
-
Repl 2018-05-21
-
(copied to CRM)
-
15
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