[SERVER-82974] Segfault using 3.6.17 with mmapv1 Created: 08/Nov/23 Updated: 08/Nov/23 Resolved: 08/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dan J | Assignee: | Chris Kelly |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Seeing the following segfault, this is happening quite frequently on primary only. The mapped+journal is around 1T and half for mapped, resident is around 230GB and virtual mem usage is around 1.00T. The server has 256GB physical and is a dedicated mongo machine. It looks like the segfault is happening when creating NewObject based on the addr2line output below. Would appreciate any kind of input to reveal the problem.
Kernel version 5.10.68 |
| Comments |
| Comment by Chris Kelly [ 08/Nov/23 ] |
|
Unfortunately, there's not much we can do to help with your issue on this unsupported version. Specifically:
It's possible that you may come across useful information on other, old SERVER tickets in our Jira. Beyond that, I'd have to recommend you to start by asking our community for help by checking the MongoDB Developer Community Forums. If the discussion there leads you to suspect a bug in a supported version of MongoDB (4.4+), then we'd want to investigate it as a possible bug here in the SERVER project.
|
| Comment by Dan J [ 08/Nov/23 ] |
|
chris.kelly@mongodb.com There are some obstacles to upgrading the Mongo at the moment to V4.4+ for us and is not an option I can explore. Our first step would be to determine if this could be resolved without upgrading and if you can help shed some lights on the cause of the current issue, I would be very much appreciated. |
| Comment by Chris Kelly [ 08/Nov/23 ] |
|
MongoDB 3.6 reached end of life in April 2021 and is no longer supported. Can you please upgrade to MongoDB v4.4+ and see if your issue persists? Notably, we have long since migrated from MMAP to the WiredTiger storage engine. Christopher |