Details
-
Bug
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
Correctness
-
ALL
-
11
Description
Other parts of resmoke (such as ContinuousStepdown) assume stopping a process does not wait for it to exit cleanly. In this particular case, this is to immediately step up a secondary after the old primary has been shutdown, so that availability is restored as fast as possible.
This is already the case for the non-Windows implementation, but for some unknown reason for mongod, in TERMINATE mode in Windows, resmoke waits up to 60 seconds. This causes sporadic test failures due to a primary not being found.
Attachments
Issue Links
- is related to
-
SERVER-25358 resmoke does not terminate mongod cleanly on Windows
-
- Closed
-