Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 4.3.4
Affects Version/s: None
Component/s: Replication
Labels:
- datarepl3.2

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Repl 2020-02-24, Repl 2020-03-09
Linked BF Score:
0

Another way to look at this is that we should only report if we are secondary, and report when we become secondary in addition.

is depended on by

SERVER-45997 Test re-sync cases where nodes can roll back majority committed writes

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

Assignee:: Vesselina Ratcheva (Inactive)

Reporter:: Matt Dannenberg

Participants:: Githook User, Matt Dannenberg, Vesselina Ratcheva, William Schultz

Votes:: 0 Vote for this issue

Watchers:: 11 Start watching this issue

Created:: Apr 08 2015 04:51:29 PM UTC

Updated:: Feb 28 2020 12:04:26 AM UTC

Resolved:: Feb 28 2020 12:04:26 AM UTC