-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Testing Infrastructure
-
None
-
Fully Compatible
-
ALL
-
Repl 2020-06-15, Repl 2020-07-13, Repl 2020-07-27, Repl 2020-08-10
The changes from a417e97 as part of SERVER-39172 made it so MongoRunner.stopMongod() skips calling wait_for_pid() in shell_utils_launcher.cpp. It is then the responsibility of ReplSetTest#stopSet() to actually wait for the mongod processes to finish terminating. However, it doesn't do anything with the returned exitCode other than logging its value.
ReplSetTest#stopSet() should throw a JavaScript exception in a similar fashion to MongoRunner.stopMongod().
// If we are not waiting for shutdown, then there is no exit code to check. if (!waitpid) { return 0; } if (allowedExitCode !== returnCode) { throw new MongoRunner.StopError(returnCode); } else if (returnCode !== MongoRunner.EXIT_CLEAN) { print("MongoDB process on port " + port + " intentionally exited with error code ", returnCode); }
- is caused by
-
SERVER-39172 Shut down mongod nodes in parallel in ReplSetTest
- Closed