[SERVER-4190] SEGFAULT doing query Created: 02/Nov/11 Updated: 30/Mar/12 Resolved: 14/Nov/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.0.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Myers Carpenter | Assignee: | Aaron Staple |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOS 64-bit |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | Linux | ||||||||
| Participants: | |||||||||
| Description |
|
Out of the blue, the PRIMARY crashed and left itself listening for connections but not replying to anything, causing automatic fail over to not work.
I'm either misreading the log or it's confused about the _id index on "data_visualization.conversations.content_set_report.active_path_funnel_forks" because db.data_visualization.conversations.content_set_report.active_path_funnel_forks.getIndexes() returns
Full log attached. |
| Comments |
| Comment by Aaron Staple [ 14/Nov/11 ] |
|
Looks like the cause is |
| Comment by Eliot Horowitz (Inactive) [ 06/Nov/11 ] |
|
Can you send a list of databases and collections from the node that crashed? |
| Comment by Andrew Harbick [ 06/Nov/11 ] |
|
That is correct. We have a situation where one of our replicas (2.0.1) can be crashed by doing a mongodump using the 1.6.5 mongodump utility and it produced the above stack trace. Two things: I'm not sure if we've rebuilt that replica yet off the master (it's only on a testing system right now) but I'm pretty sure that if we rebuilt it from the master everything will be back to normal... Just wanted to call out that: |
| Comment by Eliot Horowitz (Inactive) [ 06/Nov/11 ] |
|
Something is also odd as direct queries on indexes shouldn't be done like that. I think this is probably a bug in the 1.6.5 mongodump doing something it shouldn't. |
| Comment by Eliot Horowitz (Inactive) [ 06/Nov/11 ] |
|
Just to be clear, mongodump version 1.6.5 is crashing server version 2.0.1 with the above stack trace? |
| Comment by Andrew Harbick [ 02/Nov/11 ] |
|
OK... I'm pretty sure this issue is related to https://jira.mongodb.org/browse/SERVER-2973 That is: So... While we can get around the problem just by using the latest version of mongodump it feels kinda bad that we can kill our database with the wrong version. Myers is going to try to come up with a concise way to cause the problem. |
| Comment by Andrew Harbick [ 02/Nov/11 ] |
|
It should be noted that the name kinda undersells this issue... It's definite "Bad TM" that the server crashes on a query. What's worse though is that the server doesn't stop listening and the automatic failover to other replicas didn't happen. |