[SERVER-63990] Segmentation fault on primary Created: 25/Feb/22 Updated: 10/Jun/22 Resolved: 10/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tejas Jadhav | Assignee: | Edwin Zhou |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
We have a MongoDB cluster setup with following configuration
Throughput pattern is write heavy with comparatively lesser number of reads. A few days back, our primary crashed out of nowhere. It emitted the following traceback,
|
| Comments |
| Comment by Edwin Zhou [ 10/Mar/22 ] |
|
We haven’t heard back from you for some time, so I’m going to close this ticket. If you find this is still an issue for you after upgrading to a supported version and working with our developer community forums, then we'd want to investigate it as a possible bug here in the SERVER project. Best, |
| Comment by Dmitry Agranat [ 27/Feb/22 ] |
|
Hi tejas.jadhav@gojek.com, As MongoDB 3.6 has reached EOL on April 2021, we'd like to encourage you to start by asking our community for help by posting on the MongoDB Developer Community Forums. If the discussion there leads you to suspect a bug in the MongoDB supported versions, then we'd want to investigate it as a possible bug here in the SERVER project. Regarding the mentioned segmentation fault, this might be related to Regards, |