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

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.3, 3.5.3
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v3.4
    • Sprint:
      Repl 2017-02-13
    • Linked BF Score:
      0

      Description

      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.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: