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

Only restart scheduled heartbeats

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.8.0, 4.9.0, 4.4.4
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Repl 2020-09-07, Repl 2020-09-21, Repl 2020-10-05, Repl 2020-10-19, Repl 2020-11-02, Repl 2020-11-16
    • 19

      After SERVER-29030, we cancel our own heartbeat requests if we receive a heartbeat request that announces a new primary. Since we don't update our knowledge of the primary when we receive a heartbeat request, it seems possible to continuously schedule and cancel our heartbeat requests. As a result, a node in initial sync may not be able to find a sync source, because it has not successfully received 2N heartbeats from other nodes, and eventually the node will shut down.

            Assignee:
            xuerui.fa@mongodb.com Xuerui Fa
            Reporter:
            xuerui.fa@mongodb.com Xuerui Fa
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: