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

XMLWordPrintableJSON

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

      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
            Reporter:
            Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: