[SERVER-16161] log heartbeat failures and cause Created: 14/Nov/14 Updated: 04/Dec/14 Resolved: 03/Dec/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 2.8.0-rc2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
When we set a node as "down" due to a failed heartbeat, we currently log nothing at debug log level 0. It's hard to tell why a primary stepped down, for instance. |
| Comments |
| Comment by Githook User [ 03/Dec/14 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Eric Milkie [ 19/Nov/14 ] |
|
Node state changes were fixed in |