I still see this log when I start ES (v2.3.5) even though I have these settings in /etc/security/limits.conf, and have rebooted the machine. I also have bootstrap.mlockall: true in /etc/elasticsearch.yml. [2016-10-04 18:51:22,933][WARN ][bootstrap ] These can be adjusted by modifying…

Memlock settings not taking effect?

ZillaG (ZillaG) October 6, 2016, 7:25pm 5

Yes, of course he elasticsearch.yml file was updated when i installed v2.4.1

Topic		Replies	Views
Help getting mlockall to work on ubuntu 14.04 Elasticsearch	4	6846	July 5, 2017
Memlock check is incorrect in v2.3.1 Elasticsearch	1	1059	December 5, 2017
Unknown mlockall error 0 Elasticsearch	11	1056	July 6, 2017
Cannot set up mlockall 'true' on RedHat 6.6 Elasticsearch	14	4035	July 5, 2017
How do I enable mlockall on Linux? Elasticsearch	3	6109	July 5, 2017

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

Memlock settings not taking effect?

Related topics