[SERVER-16629] primary server fassert() with fatal assertion 16967 Created: 22/Dec/14 Updated: 09/Apr/15 Resolved: 02/Mar/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 2.6.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Boris HUISGEN | Assignee: | Ramon Fernandez Marina |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | crash, replicaset, replication | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Debian 7.7 / MongoDB 2.6.6 from 10gen repository |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
We have a replicat set of 3 servers MongoDB 2.6.6. Yesterday the primary server has crashed with this assertion :
Server won't restart (same assertion after 10/15 seconds). Is it a data / indexes corruption ? I'm already on production, any help will be appreciate ... |
| Comments |
| Comment by Ramon Fernandez Marina [ 23/Jan/15 ] |
|
bhuisgen, are you still running into this issue or have you been able to re-sync this node from a healthy primary? If this is still an issue for you, can you please upload full logs for the affected node(s) when it happens? Thanks, |
| Comment by Daniel Pasette (Inactive) [ 23/Dec/14 ] |
|
Many deployments in AWS using EBS. Should not ordinarily be a correctness problem as long as the performance characteristics are fine for your use case. |
| Comment by Boris HUISGEN [ 23/Dec/14 ] |
|
Ok, it's probably a problem with EBS disks (EC2 instances type m3.medium with a dedicated EBS for mongo). Are EBS disks really advised for a stable environment ? The easiest for me is to move to local SSD disks... |
| Comment by Ramon Fernandez Marina [ 22/Dec/14 ] |
|
I forgot to add: there's an open ticket ( Also, the lines above the "Fatal Assertion 16967" error message typically contain further information. In fact, it would be good if you could upload logs from this primary from startup to fassert(), to try to rule out other issues. |
| Comment by Ramon Fernandez Marina [ 22/Dec/14 ] |
|
Hi bhuisgen, this assertion may indeed be triggered by data corruption, often caused by a faulty disk. If you run mongod --repair chances are you'll see the same assertion, but since you have a replica set I'd recommend you resync from a healthy node. Please check the health of your disks as well. |