[SERVER-27908] log every heartbeat during testing Created: 03/Feb/17  Updated: 27/Jun/18  Resolved: 09/Mar/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.5.5

Type: Improvement Priority: Major - P3
Reporter: Judah Schvimer Assignee: William Schultz (Inactive)
Resolution: Done Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-30501 Create rollback logging component Closed
related to SERVER-32906 Improve logging around elections Closed
related to SERVER-29608 improve debug heartbeat log messages Backlog
is related to DOCS-9988 Document new replication heartbeats l... Closed
is related to SERVER-32907 Turn heartbeat log verbosity back dow... Closed
Backwards Compatibility: Minor Change
Backport Requested:
v3.4
Sprint: Repl 2017-03-06, Repl 2017-03-27
Participants:
Linked BF Score: 15

 Description   

Heartbeats failing or timing out are a very common source of build failures. Since they only happen every 2 seconds, logging 1-4 messages per heartbeat will not explode the number of log messages we have.

Currently we only log very long running heartbeats or at higher log levels. At the maximum, this would be when a heartbeat is sent, when it is received, when the response is sent, and when the response is received, though all four of these may not be necessary. Logging when we cancel heartbeats may also be worthwhile.

This can also be done to a special log component so that it's easy to turn on/off and easy to filter out in log readers. Also some of the log messages in this component could be at higher log levels than others.



 Comments   
Comment by Githook User [ 09/Mar/17 ]

Author:

{u'username': u'will62794', u'name': u'William Schultz', u'email': u'william.schultz@mongodb.com'}

Message: SERVER-27908 Log every heartbeat during testing
Branch: master
https://github.com/mongodb/mongo/commit/4bda560cd9b0061afa83e097ad9196b1ac76b073

Comment by Spencer Brody (Inactive) [ 13/Feb/17 ]

We should do this by adding a replication.heartbeats log component whose verbosity can be controlled independently.

Generated at Thu Feb 08 04:16:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.