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

Change catchup.js to be resilient to replSetStepUp failing because the node is already a candidate

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.3, 3.5.3
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • v3.4
    • Repl 2017-02-13
    • 0

      Catchup.js disconnects and then reconnects the primary and a secondary. Then later on it tries to step up a secondary. This stepUp can fail if the secondary stepping up is the same one that was temporarily disconnected from the primary and it had tried to run for election during that time.

            Assignee:
            spencer@mongodb.com Spencer Brody (Inactive)
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: