[SERVER-9550] Starting server during shutdown flush causes crash Created: 03/May/13 Updated: 24/Jan/15 Resolved: 23/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 2.2.4, 2.4.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierre Dane | Assignee: | Victor Hooi |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 2008 R2 |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
after shutting down mongod with db.shutdownServer(), if one tries to start up the server again before the flush has completed and the lock file removed, the shutdown does not complete cleanly, and the data is corrupted. |
| Comments |
| Comment by Ramon Fernandez Marina [ 27/Jun/14 ] |
|
pierrearmageddon, we haven't heard back from you for a while. Are you still experiencing this issue? If the answer is yes, can you please provide the additional information requested by victor.hooi above so we can try to reproduce it on our end? Thanks, |
| Comment by Victor Hooi [ 19/Mar/14 ] |
|
pierrearmageddon My apologies that we haven't followed this up earlier. I'm currently trying to reproduce this error and need some additional information. Firstly, can I confirm if you have seen this error at all since the initial report? And if so, on what versions of MongoDB please? Second, you mentioned database corruption - are you able to provide any more details on what sort of corruption was exhibited (e.g. missing documents, missing fields, log files, or was the database completely unreadable?) Thanks, |
| Comment by Pierre Dane [ 16/May/13 ] |
|
Nope - we aren't running with journal as we don't have a spare bay on this particular server for a separate journal disk, and using the same SSD caused massive performance impact. Thu May 16 10:21:39 dbexit: shutdown called
Thu May 16 10:21:57 [initandlisten] MongoDB starting : pid=5220 port=3006 dbpath=F:\data\attributestore 64-bit host=mongo80 Thu May 16 10:21:57 [initandlisten] exception in initAndListen: 13627 Unable to create/open lock file: F:\data\attributestore\mongod.lock The process cannot access the file because it is being used by another process.. Is a mongod instance already running?, terminating
|
| Comment by Scott Hernandez (Inactive) [ 03/May/13 ] |
|
Are you not running with journaling (which is on by default)? Can you supply the full logs please? |