-
Notifications
You must be signed in to change notification settings - Fork 25.8k
mlockall: false despite being configured #9357
Copy link
Copy link
Closed
Labels
:Delivery/PackagingRPM and deb packaging, tar and zip archives, shell and batch scriptsRPM and deb packaging, tar and zip archives, shell and batch scripts>docsGeneral docs changesGeneral docs changesTeam:DeliveryMeta label for Delivery teamMeta label for Delivery teamhelp wantedadoptmeadoptme
Metadata
Metadata
Assignees
Labels
:Delivery/PackagingRPM and deb packaging, tar and zip archives, shell and batch scriptsRPM and deb packaging, tar and zip archives, shell and batch scripts>docsGeneral docs changesGeneral docs changesTeam:DeliveryMeta label for Delivery teamMeta label for Delivery teamhelp wantedadoptmeadoptme
Type
Fields
Give feedbackNo fields configured for issues without a type.
Lots of details below, but the general problem here is that mlockall is not being applied despite all settings being applied as per the config docs.
From the logs
[2015-01-18 17:32:48,613][WARN ][common.jna ] Unable to lock JVM memory (ENOMEM). This can result in part of the JVM being swapped out. Increase RLIMIT_MEMLOCK (ulimit).From the _nodes API;
"max_file_descriptors" : 65535,And the outcome is;
The last one is
process.mlockall.