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

step down should resend heartbeats if secondaries are not caught up

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.1.9
    • Replication
    • None
    • Fully Compatible
    • ALL
    • RPL A (10/09/15)
    • 0

    Description

      When a primary is requested to step down without

      {force: true}

      and secondaries are not caught up, it has to wait until the previously scheduled heartbeats are run to obtain updated liveness information on the secondaries before completing the step down process. This may take a while with a long heartbeat interval. Restarting the heartbeats if the primary cannot step down immediately will ensure that we get the most update information on the secondaries in the cluster.

      Attachments

        Issue Links

          Activity

            People

              benety.goh@mongodb.com Benety Goh
              benety.goh@mongodb.com Benety Goh
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: