[SERVER-7038] Mongo 2.2.0 Replica Set Primary Node Crashes Created: 13/Sep/12 Updated: 08/Mar/13 Resolved: 05/Nov/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vinayak Javaly | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
EC2 |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
We recently upgraded from 2.0 to 2.2, and several of our replica sets have had 1 or more nodes crash. An example is, in a 6-node replica set, the primary has crashed twice today. Bottom of mongod.log output below: Thu Sep 13 16:38:58 Invalid access at address: 0x7fc305dde720 from thread: Thu Sep 13 16:38:58 Got signal: 11 (Segmentation fault). Thu Sep 13 16:38:58 Got signal: 11 (Segmentation fault). Thu Sep 13 16:38:58 Backtrace: |
| Comments |
| Comment by Kristina Chodorow (Inactive) [ 14/Sep/12 ] |
|
Can you attach a larger chunk of the log? (The last couple hundred lines would be helpful.) Can you also attach the log from another time it crashed? |