[SERVER-21504] Lower log verbosity at level 0 when replica set member is unavailable Created: 17/Nov/15  Updated: 25/Nov/15  Resolved: 18/Nov/15

Status: Closed
Project: Core Server
Component/s: Networking, Replication
Affects Version/s: 3.2.0-rc3
Fix Version/s: 3.2.0-rc4

Type: Improvement Priority: Major - P3
Reporter: James Wahlin Assignee: Adam Midvidy
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-16148 Replica logs excessively when other m... Closed
Related
Backwards Compatibility: Fully Compatible
Sprint: Platform C (11/20/15)
Participants:

 Description   

When one member of a 3 member replica set is down, the remaining members will print 6 log lines every 2 seconds to indicate. We should look to cut this down to a single line per heartbeat if possible (at log level 0).

Log output for one member during one 2 second interval:

2015-11-17T12:21:05.110-0500 I ASIO     [NetworkInterfaceASIO] Failed to connect to James-Wahlin-MacBook-Pro.local:27017 - HostUnreachable Connection refused
2015-11-17T12:21:05.111-0500 I REPL     [ReplicationExecutor] Error in heartbeat request to James-Wahlin-MacBook-Pro.local:27017; HostUnreachable Connection refused
2015-11-17T12:21:05.113-0500 I ASIO     [NetworkInterfaceASIO] Failed to connect to James-Wahlin-MacBook-Pro.local:27017 - HostUnreachable Connection refused
2015-11-17T12:21:05.113-0500 I REPL     [ReplicationExecutor] Error in heartbeat request to James-Wahlin-MacBook-Pro.local:27017; HostUnreachable Connection refused
2015-11-17T12:21:05.116-0500 I ASIO     [NetworkInterfaceASIO] Failed to connect to James-Wahlin-MacBook-Pro.local:27017 - HostUnreachable Connection refused
2015-11-17T12:21:05.116-0500 I REPL     [ReplicationExecutor] Error in heartbeat request to James-Wahlin-MacBook-Pro.local:27017; HostUnreachable Connection refused



 Comments   
Comment by Githook User [ 18/Nov/15 ]

Author:

{u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}

Message: SERVER-21504 NetworkInterfaceASIO logging tweaks

Comment by James Wahlin [ 17/Nov/15 ]

This issue is two-fold. The first is the duplication between NetworkInterfaceASIO and ReplicationExecutor. The second is that we print the same message in both 3 times (which I am guessing is initial attempt + 2 retries?).

Comment by Adam Midvidy [ 17/Nov/15 ]

Although the ASIO log message is redundant w.r.t. replication heartbeating, it is useful for other ASIO consumers such as the TaskExecutor. However, I can see how the ReplicationExecutor message is more useful than just seeing that ASIO failed to connect. Not really sure what the best option is here.

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