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

raise timeout for priority takeover in replsets_priority1.js

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.13, 3.3.14
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Backport Requested:
      v3.0
    • Sprint:
      Repl 2016-09-19
    • Linked BF Score:
      0

      Description

      replsets_priority1.js only waits 60 seconds for a priority takeover; however, when only two nodes of a three node set are up, and the higher priority node (in secondary state) is behind the lower priority node (in primary state), and the higher priority node's sync source was previously the third node (that is now down), it can take quite a while for the higher priority node to switch sync sources, catch up, and successfully run for election as a priority takeover.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: