CPU usage caused by abnormal MongoDB Shutdown

After the development machine (win7) is shut down abnormally, MongoDB cannot be started normally at the next startup, while mongodProgramWill keep trying to start MongoDB

In this way, the CPU is abnormal and busy. After checking for half a day, it may be caused by MongoDB.

Open the MongoDB log directory, and the log file has been added to 1 GB +

Then, open the MongoDB data file and delete the mongod. Lock file (if the file exists during restart, the restart will fail !)

Open the command line and run mongod -- repair.

Restart the MongoDB service. The service is normal and the CPU usage is stable to less than 10%.