[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.
We should log when we take note of a change in a remote node's state. I would also consider logging when heartbeats fail, and the reason why (TCP disconnect vs. timeout).



 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: SERVER-16161 Log failed heartbeat requests at default verbosity
Branch: master
https://github.com/mongodb/mongo/commit/3b1d97d430a229bf57c46bc7bc4977801b5bb553

Comment by Eric Milkie [ 19/Nov/14 ]

Node state changes were fixed in SERVER-16008; it would still be helpful to log heartbeat failures so we know why an election was triggered at a particular time.

Generated at Thu Feb 08 03:40:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.