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

log heartbeat failures and cause

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.8.0-rc2
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • ALL

      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).

            Assignee:
            spencer@mongodb.com Spencer Brody (Inactive)
            Reporter:
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: