[SERVER-23441] MongoDB crashing with Fatal Assertion 28558 Created: 31/Mar/16 Updated: 27/Mar/17 Resolved: 06/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.2.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Richard Burton | Assignee: | Kelsey Schubert |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
Here's the full stack trace in the console: Mongo was executed using simply mongod --dbpath . to paginate over a collection in 200 records at a time and after each record is processed, I issue an update. The drive is 2TB in size so space shouldnt be an issue unless there's another path being used.
|
| Comments |
| Comment by Kelsey Schubert [ 06/May/16 ] |
|
We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide the details about your storage layer in a comment and we will reopen the ticket. Regards, |
| Comment by Kelsey Schubert [ 25/Apr/16 ] |
|
We still need the answers to my questions above to diagnose the problem. If this is still an issue for you, can you please provide the requested details about your storage layer? Thank you, |
| Comment by Kelsey Schubert [ 31/Mar/16 ] |
|
Thank you for reporting this behavior. Please answer the following questions so we can get better understanding of what is going on here.
Kind regards, |