Bootstrap.mlockall: true in elastisearch not take effect?

figo10203 · August 9, 2016, 9:11am

Hi, as es official web site stated, it is strongly recommend that bootstrap.mlockall: true should be set in elasticsearch.yaml file. but after restart es, I find that the setting is not effective as below graph

es is restarted with an user rui rather than root, I doubt that rui has no permission to make bootstrap.mlockall: true to take effect. So what I can do with that?

Any help will be appreciated!

Thanks a lot in advance

warkolm · August 10, 2016, 2:06am

Where did you set it? Did you set heap min/max the same?

figo10203 · August 10, 2016, 3:24am

I set the property in elasticsearch.yml as below graph

For heap, I set the envrionment ES_HEAP_SIZE=3g.
And I start ES by the user rui with Supervisord

warkolm · August 10, 2016, 5:22am

Please don't post pictures of text, they are difficult to read and some people may not be even able to see them.

figo10203 · August 10, 2016, 6:34am

Hi warkolm,I set the property in /opt/modules/elasticsearch-2.3.3/conf/elasticsearch.yml as bootstrap.mlockall: true, and restart es via supervisord, the conf of which is as
command=/opt/modules/elasticsearch-2.3.3/bin/elasticsearch --network.host 0. 0.0.0
user=rui
but after restarting, I see the below result in _nodes/process?pretty:

"M_r6PeG4TraVpfUeoZnmOA" : {
"name" : "node-2",
"transport_address" : "10.172.95.65:9300",
"host" : "10.172.95.65",
"ip" : "10.172.95.65",
"version" : "2.3.3",
"build" : "218bdf1",
"http_address" : "10.172.95.65:9200",
"process" : {
"refresh_interval_in_millis" : 1000,
"id" : 10305,
"mlockall" : false
I want to ask why?

Thanks a lot!