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

ReplSetTest should always awaitSecondaryNodes() at the end of initiate

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.4.4, 3.5.6
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2017-04-17
    • 0

    Description

      when initiate was broken up into initiateWithAnyNodeAsPrimary() and initiateWithNodeZeroAsPrimary(), initiateWithAnyNodeAsPrimary() lost the call to awaitSecondaryNodes() at the end. This was necessary to make sure initiate actually finished before moving on with the test.

      Attachments

        Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. SERVER-28376 ReplSetTest.initiate() should call awaitReplication before requesting node 0 to step up as primary

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: