[SERVER-18641] mongodb process crashes on insert with WiredTiger Panic error Created: 24/May/15 Updated: 04/Jun/15 Resolved: 29/May/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Homam Hosseini | Assignee: | Ramon Fernandez Marina |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | This keeps happening when importing data with `mongorestore` |
| Participants: |
| Description |
Mongodb started with `mongod -f /etc/mongodb.conf --wiredTigerEngineConfigString="hazard_max=10000" --fork`
Log after crash:
|
| Comments |
| Comment by Ramon Fernandez Marina [ 29/May/15 ] | |
|
homam, if I understand correctly we may not be able to diagnose this issue any more. If you still have logs for the affected mongod you may be able to see what subsequent restarts did with respect to the affected data; you may also want to look in your system logs for possible errors from your storage subsystem, which could also have played a part in this problem. I'm going to resolve this ticket, but if this happens again it would be very useful if you could immediately collect logs for the mongod process and save the data you're restoring for further investigation. Regards, | |
| Comment by Homam Hosseini [ 26/May/15 ] | |
|
1. No it happens on a collection with more than 900,000,000 records. The collection has indexes on 5 properties. 2. Yes it was running 3.0.0 before. 3. Unfortunately I lost the specific dump that was causing the problem. I can tell you that this crash was happening with not just one specific dump. I was able to make it working by: dumping and restoring the whole collection and then restoring the new dumps that was causing the problem. (it took almost 24 hours) I think this problem started happening after I deleted some records from the collection. We restore ~400,000 records into this collection every half an hour, 48 times a day for the past 3 months and never had this problem before. | |
| Comment by Ramon Fernandez Marina [ 25/May/15 ] | |
|
homam, we'll need some more information to diagnose this issue:
It may also help for you to send us the data you're restoring and the exact mongorestore command line you're using so we can try to reproduce the problem on our end. You can upload data securely and privately via scp:
where "<filename>" is a tar/zip archive of your data. When prompted for a password just press enter. Thanks, |