[SERVER-28042] log when a node marks another node as down Created: 17/Feb/17 Updated: 06/Dec/17 Resolved: 17/May/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.8 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Matthew Russotto |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Repl 2017-03-27, Repl 2017-04-17, Repl 2017-05-08, Repl 2017-05-29 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
We log when a node thinks another node has changed state in the "up" case here. We should add in the down case to be less confusing. |
| Comments |
| Comment by Githook User [ 17/May/17 ] |
|
Author: {u'username': u'mtrussotto', u'name': u'Matthew Russotto', u'email': u'matthew.russotto@10gen.com'}Message: |
| Comment by Judah Schvimer [ 17/Feb/17 ] |
|
The two places we call setDownValues are here and here. We should remove the log messages around those calls that are at higher log levels to not log extraneously. |