-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 1.8.2
-
Component/s: Internal Code
-
Environment:Windows 7 64 bit, Mongo 64 bit
-
Windows
I have MongoDB set up as a Windows Service. If Windows crashes, MongoDB has a lock file in the data directory that causes the server to use 100% CPU and write continuously to the log file. This happens even if Mongo was never used. Currently the only solution is to disable the service and delete the lock file.
- is duplicated by
-
SERVER-3942 MongoDB service on Windows infinitely restarts when server goes down abnormally
- Closed
- is related to
-
SERVER-4373 Windows service should "do the right thing" after a crash
- Closed