[SERVER-36600] mongos failed on error - Failed to mlock: Unknown error Created: 12/Aug/18 Updated: 27/Oct/23 Resolved: 14/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 4.0.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | jiancai.hao | Assignee: | Dmitry Agranat |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
I installed mongodb in sharding, but the mongos process was down suddenly not long after the start. There's error in the log file: 2018-08-11T22:11:18.010+0800 I NETWORK [listener] connection accepted from ***aborting after fassert() failure 2018-08-11T22:11:18.051+0800 F - [conn1275] Got signal: 6 (Aborted). ... |
| Comments |
| Comment by Dmitry Agranat [ 14/Aug/18 ] |
|
Thank you for the clarification sword2000 |
| Comment by jiancai.hao [ 13/Aug/18 ] |
|
Thanks Dmitry, Yes, this maybe one factor. I have set locked memory as the recommended value. At the same time, I found the direct cause – in one of my client, there is a NoSQLBooster for mongoDB process who is false death and is continously connecting to this mongos server, so that the mongos server exhausted all the locked memory in seconds. I think this ticket can be closed now. Thanks. |
| Comment by Dmitry Agranat [ 12/Aug/18 ] |
|
Hi sword2000, The reported error suggests that the ulimit max locked memory setting is not set to our recommended value. Please adjust the ulimit settings for max locked memory and try starting the node again to see if that resolves the issue. Thanks, |