[SERVER-14869] Mongodb crashes without log after creating index Created: 12/Aug/14 Updated: 10/Dec/14 Resolved: 12/Aug/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaz | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | Do continously massive insertions > 3Gb/h and create indexes on one of the newly created collections. |
||||||||
| Participants: | |||||||||
| Description |
|
Hello, I do massive inserts (about 3Gb/h). When I create indexes (background=True), SOMETIMES my server crashes without any trace on the log files. Moreover, I am not sure that this only due to indexes.... I got 2 different errors :
I did not have this error before, but since I have changed the dbpath to another one in a share drive, it is not stable anymore ! Besides, I have also tried to set this option to true: smallFiles, but I got the same problem. Do you have any idea ? The configuration file is: Server :
|
| Comments |
| Comment by Kaz [ 13/Aug/14 ] |
|
I have added a thread on StackOverflow as well if you prefer. Thanks |
| Comment by Kaz [ 13/Aug/14 ] |
|
Thank you very much for your answer. I have spent the whole day yesterday understanding the error and looking at the stack overflow threads. I have not found anything about this error, that's why I think this is a bug on the server. keyUpdates:0 numYields:0 reslen:164 858ms I tried the repair command but it would take days for me (several dozens of Gb ) so I stopped. And I started again the DB, and I had the same issue. |
| Comment by Ramon Fernandez Marina [ 12/Aug/14 ] |
|
Looks like your database files and your logs are both on a network drive, which means that if there's a problem with the network (or the network drive) mongod may not be able to write anything in the logs, and without logs it's quite difficult to diagnose problems. If you are planning to put your database files on a network drive, I would suggest you consider using a local drive for your logs, so if there's a problem you can gather more information about it. Note also that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server and tools. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-user group. If after obtaining logs you find a bug in MongoDB please feel free to open a new SERVER ticket and upload the logs to it. Finally, the "out of disk space" message may not be completely accurate in this case, so I've opened |