Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-21504

Lower log verbosity at level 0 when replica set member is unavailable

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.2.0-rc3
    • Fix Version/s: 3.2.0-rc4
    • Component/s: Networking, Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Epic Link:
    • Sprint:
      Platform C (11/20/15)

      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
      

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: