[SERVER-4257] Random segfault Created: 11/Nov/11 Updated: 11/Nov/11 Resolved: 11/Nov/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 2.0.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Paul Harvey | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | crash | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 10.04.3 LTS on an 8GB single core VM db version v2.0.0, pdfile version 4.5 Single mongod stand-alone, no replica sets or sharding, running a Foswiki installation using the perl MongoDB driver. |
||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
mongod segfaulted apparently for no reason (unable to correlate this with anything remarkable in the application logs). For some reason it was building indexes just before the crash. Not sure why it was doing that (nothing in the application's log suggested an action that would have triggered this). As you can see from the logs, there are some truly nasty queries, a lot of suboptimal stuff going on. I've got some big improvements in the pipeline but they're not deployed yet. As a result of this crash I've upgraded to mongod 2.0.1 and am now setting up MMS. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 11/Nov/11 ] |
|
This is a version of |
| Comment by Paul Harvey [ 11/Nov/11 ] |
|
For what it's worth this DB has run flawlessly for at least three months now. |