last_vote.js should use ReplSetTest::stepUp() on node 1 before reconfig

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 3.4.5, 3.5.6
    • Affects Version/s: None
    • Component/s: Replication
    • Fully Compatible
    • ALL
    • v3.4
    • Repl 2017-04-17
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Preventing node 0 from running for election for 5 seconds before doing a reconfig is not enough time to ensure node 1 is elected. We also do not do any waitForState on node 1 to make sure it is actually primary.

      To address this we should increase the timeout in the stepdown before node 0 is able to become primary and actually wait for node 1 to become primary before doing the reconfig. We can then use a replSetFreeze: 0 to reset the election timeout on node 0. Using ReplSetTest::stepUp could fix this. We also should make sure node 1 is actually elected primary before doing the reconfig. Asserting that node 0 is secondary is not enough.

            Assignee:
            Will Schultz
            Reporter:
            Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: