[SERVER-23396] wiredTiger STORAGE Assertion Created: 29/Mar/16 Updated: 29/Mar/16 Resolved: 29/Mar/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | joe piscitella | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
3.5.0-51-generic #77~precise1-Ubuntu SMP Thu Jun 5 00:48:28 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
| Comments |
| Comment by Ramon Fernandez Marina [ 29/Mar/16 ] |
|
Thanks for uploading the log jpiscitella. The errors you were seeing indicate that data in the collection-6--6088918010050475399.wt somehow got corrupted. The most common culprit is errors at the storage layer, so I'd recommend you search your system logs for storage-related error messages and check the health of your storage layer to make sure this doesn't happen again. Since you've rebuilt this node there's not much we can do in terms of troubleshooting, so I'm going to close this ticket. If this happens again it would be helpful if you could save a copy of the data in your dbpath for further investigation. Regards, |
| Comment by joe piscitella [ 29/Mar/16 ] |
|
mongod terminated and wouldn't restart. since this was a member of a replica set I just rebuilt from the primary. the environment was our test environment that we updated from 3.0.6 to 3.0.10 this weekend. log2 file attached as requested |
| Comment by Ramon Fernandez Marina [ 29/Mar/16 ] |
|
jpiscitella, I've moved this ticket for the SERVER project, since you've run into this issue using MongoDB and not standalone WiredTiger. Do you have the full logs since the last restart until you see this error in the logs? I'm looking for more details, specially what happens after the "END BACKTRACE" message. Does this node continue to operate or does it terminate? Thanks, |