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

Separate notion of 'down' and 'unknown' in heartbeat liveness monitoring

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None
    • Replication

    Description

      When a node first starts up, it has no idea the state of the other nodes in the replica set. Currently it defaults to assuming all nodes are 'down' until it gets a heartbeat proving otherwise. This can sometimes cause nodes to call for elections unnecessarily. Instead we should consider nodes in state 'unknown' until the heartbeat timeout passes without hearing from them, and not call for an election so long as any nodes are still in state 'unknown'.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: