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

liveness timeout is only rescheduled on replSetUpdatePosition commands

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

      We cancel and reschedule the liveness timeout when we receive replSetUpdatePosition commands. We update liveness information on heartbeats as well, but don't cancel and reschedule the liveness timeout. There does not seem to be a reason for this inconsistency; we should either always reschedule it, or never reschedule it until we timeout and check if we need to step down.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: