Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Done
-
None
-
Fully Compatible
-
ALL
-
Repl 2020-02-24, Repl 2020-03-09
-
0
Description
Another way to look at this is that we should only report if we are secondary, and report when we become secondary in addition.
Attachments
Issue Links
- is depended on by
-
SERVER-45997 Test re-sync cases where nodes can roll back majority committed writes
-
- Closed
-
- is documented by
-
DOCS-13463 Investigate changes in SERVER-17934: Do not report upstream progress while in state STARTUP2
-
- Closed
-
- is duplicated by
-
SERVER-32237 Nodes that cannot become primary must neither update progress nor vote "aye"
-
- Closed
-
- is related to
-
SERVER-18511 Report upstream progress when initial sync completes
-
- Closed
-
-
SERVER-45995 Test that nodes in initial sync maintain and gossip the commit point
-
- Closed
-
- related to
-
SERVER-19244 Secondary position information can be erroneous if nodes leave and rejoin a cluster with less data than before
-
- Closed
-