[SERVER-3582] Mongo Windows Service locks up CPU when computer reboots after a crash. Created: 11/Aug/11 Updated: 11/Jul/16 Resolved: 26/Nov/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | 1.8.2 |
| Fix Version/s: | 2.1.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ian Campbell | Assignee: | Tad Marshall |
| Resolution: | Done | Votes: | 0 |
| Labels: | crash, logging | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 7 64 bit, Mongo 64 bit |
||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Operating System: | Windows | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Tad Marshall [ 26/Nov/11 ] |
|
I posted bug |
| Comment by Tad Marshall [ 26/Nov/11 ] |
|
Fixed by commit 03cfbb50629b32c58db1cfef7e9e08e30d0c9fe6 . |
| Comment by auto [ 26/Nov/11 ] |
|
Author: {u'login': u'', u'name': u'Tad Marshall', u'email': u'tad@10gen.com'}Message: Remove (put on the wrong side of #if 1, actually) the code that was setting |
| Comment by Ian Campbell [ 18/Aug/11 ] |
|
The tail end of the log file + the lock file. You can see the server infinitely keeps restarting. |
| Comment by Chris Westin [ 12/Aug/11 ] |
|
Do you still have the log file? It might be helpful to see what mongod is writing, even just the tail end of it, if you have it. If you do, please attach it here. |