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

reconfig.js should add last node back into config before stopping the test

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Minor - P4
    • Resolution: Fixed
    • None
    • 4.3.1
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2019-11-18
    • 21

    Description

      The jstests/replsets/reconfig.js does a force reconfig to remove the last node of a 5 node replica set and then calls ReplSetTest.stopSet. If the last node transitions to REMOVED state (because it received a heartbeat with the new config) while we are trying to validate collections on that node inside stopSet, we can run into an error because the node is not in primary or secondary state. Since the test has already finished testing the necessary aspects of reconfig by the end, we can add the node back into the set before stopping the test to avoid this issue.

      Attachments

        Issue Links

          Activity

            People

              william.schultz@mongodb.com William Schultz (Inactive)
              william.schultz@mongodb.com William Schultz (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: