priority_takeover_two_nodes_equal_priority.js should use lower electionTimeoutMillis

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • ALL
    • v8.0, v7.0, v6.0
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      priority_takeover_two_nodes_equal_priority.js steps down node A and expects node B with equal priority to become the new primary. However, if for some reason node B isn't caught up in terms of oplog application, it's possible for node A to hand the election off to node C instead if node C is caught up, despite node C having lower priority.

      The test needs to call awaitReplication() and wait for all nodes to apply oplog entries. See comments

            Assignee:
            Vishnu Kaushik
            Reporter:
            Vishnu Kaushik
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: