log heartbeat failures and cause

XMLWordPrintableJSON

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

      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 Brody (Inactive)
            Reporter:
            Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: