[SERVER-12004] Mongodb process crash during reelection Created: 08/Dec/13 Updated: 10/Dec/14 Resolved: 17/Jun/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.4.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Dharshan Rangegowda | Assignee: | Ramon Fernandez Marina |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
AWS |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
There were some temporary network issues which caused a leader election. MongoDB crashed during the election Fri Dec 6 16:23:15.666 [rsMgr] replSet warning caught unexpected exception in electSelf() Fri Dec 6 16:23:15.691 Got signal: 11 (Segmentation fault). Fri Dec 6 16:23:15.695 Backtrace: |
| Comments |
| Comment by Ramon Fernandez Marina [ 17/Jun/14 ] |
|
dharshanr@scalegrid.net, we haven't heard back from you for a while so we're going to mark this ticket as resolved. If this is still an issue for you feel free to re-open the ticket. |
| Comment by Ramon Fernandez Marina [ 30/May/14 ] |
|
Is this still an issue for you? Have you tried upgrading to a newer release? There have been many improvements in this area since 2.4.1, so I'd recommend you upgrade to a newer production release. The latest release in the 2.4 branch is 2.4.10. Can you try the upgrade and let us know if the problem still persists? |