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

index_secondary_commit_after_scan_error.js should wait for the secondary before shutting it down

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.4
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Execution Team 2020-02-10
    • 145

      The test waits for the primary to finish the index build, before immediately shutting down the secondary. If the secondary hasn't yet processed the "commitIndexBuild" oplog entry to prompts an fassert, then the node will exit cleanly. The test expects the node to crash.

      Modify the test so that it does not try to shut down the secondary until it has processed the "commitIndexBuild" oplog entry.  IndexBuildTest.waitForIndexBuildToStop(secondaryDB) should be enough to fix the test.

            Assignee:
            louis.williams@mongodb.com Louis Williams
            Reporter:
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: