-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Engines - Server Integration
-
Fully Compatible
-
SESIMulan - 2026-06-30
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
There is a spurious failure where the process cleanup of the crashed mongod races against the startup of the next instance, where the latter fails because the former hasn't removed its lockfile yet.
We fix this by explicitly stopping the crashed mongod, which involves waiting on it's PID to exit (and remove the lockfile).