[SERVER-25570] Fatal Assertion on Secondary Created: 11/Aug/16 Updated: 13/Dec/16 Resolved: 13/Dec/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.2.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bob Potter | Assignee: | Kelsey Schubert |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
We are seeing a fatal assertion error on a couple of our servers. The error has happened a few times in the past week. After the first error we resynced the data on one of the replicas (in case it was a result of corruption) but it reoccurred after a couple days. We are running version 3.2.8 with the MMAPv1 storage engine. The backtrace is below, let me know if there is any additional information I can provide. Backtrace:
|
| Comments |
| Comment by Kelsey Schubert [ 13/Dec/16 ] |
|
Hi bpot, 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 additional information and we will reopen the ticket. Regards, |
| Comment by Ramon Fernandez Marina [ 13/Aug/16 ] |
|
Sorry to hear you've run into this issue bpot. This is typically indicative of data corruption on disk, which is often caused by faulty storage. What kind of servers and storage are you using? It's strange that this would happen on two different servers, but I'd recommend you run a storage health check. It would be useful to get logs for the affected nodes from the last restart until the fassert() above. Depending on what the logs show it may help to run validate() to get additional information. Thanks, |