[SERVER-27394] mongodb crash! Created: 13/Dec/16 Updated: 16/Dec/16 Resolved: 16/Dec/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.4.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Oleg Trifonov | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
| Comments |
| Comment by Kelsey Schubert [ 16/Dec/16 ] |
|
Hi nexcode, I'm glad to hear the repair process was successful. If you encounter this issue again, let us know and will continue to investigate. Please note that we recommend running MongoDB with RAID-10. Kind regards, |
| Comment by Oleg Trifonov [ 14/Dec/16 ] |
|
Now it working, but we will monitor it! |
| Comment by Oleg Trifonov [ 14/Dec/16 ] |
|
2016-12-14T04:03:27.264+0300 I STORAGE [initandlisten] finished checking dbs Now I try to start database... |
| Comment by Oleg Trifonov [ 13/Dec/16 ] |
|
1. WiredTiger on local SSD. Software raid 0 I run --repair process... It's a long time. |
| Comment by Kelsey Schubert [ 13/Dec/16 ] |
|
Hi nexcode, This assertion failure generally indicates that some or all of the data files have become corrupt in some way. It's not clear if the corruption is in the index or the data itself, and in cases like this, it's very difficult to be confident that the corruption is isolated beyond the file level. To help us understand what's going on here, I've assembled a list of routine questions about data storage and the configuration of your environment. But, please understand that it is unlikely that we will be able to determine the root cause of this issue.
To resolve this issue, I would recommend performing a initial sync, or starting mongod with --repair. Thank you, |