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

Ensure node 0 is not primary during reconfig in last_vote.js

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.2.12, 3.4.2, 3.5.2
    • Replication
    • None
    • Fully Compatible
    • ALL
    • v3.4, v3.2
    • Repl 2017-01-23
    • 0

    Description

      The test does a reconfig to make node 0 have priority 0 which fails if node 0 is primary then. We could make the test not care which node is primary after that point, but it'll lead to a more confusing and longer test. The easier solution would be to just add one more stepDown if node 0 is primary at that point.

      Attachments

        Activity

          People

            judah.schvimer@mongodb.com Judah Schvimer
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: