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

Restart heartbeats for catchup should mark all nodes restarted rather than just the scheduled ones

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Replication
    • ALL
    • 33

      Due to SERVER-50318, we only restart scheduled heartbeats. However, catchup expects all nodes to be restarted by resetting _updatedSinceRestart to false. Thus catchup may not wait for the latest heartbeats for all nodes and could exit catchup earlier. This is a regression.

      On the restart for catchup. We should call hb.restart for all nodes rather than the scheduled. Alternatively, we could restart the heartbeats for all blindly on winning an election.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            siyuan.zhou@mongodb.com Siyuan Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: