Hi all, to prevent os from swapping, it's recommended to set bootstrap.mlockall: true. I wonder the following. What happens in situations when no memory is available anymore? Does the jvm chrash in such a case? And if so, whats the benefit in using mlockall compared to swapping? Regards, Abid

The mlockall option only locks the ES JVM into RAM. The rest of the OS might still swap. If Linux completely runs out of memory it will start killing processes more or less randomly.

Ok, thanks. So setting mlockall to true just means that the jvm memory won't be swapped, it has no effect on what happens when jvm runs out or memory as it will still crash in that case. Please correct me if I'm wrong. Regards, Abid

If the application running in the JVM runs out of heap it'll obviously crash with OutOfMemoryError, but that has nothing to do with mlockall. The JVM process itself can't run out of memory once it has been locked into RAM.

Discuss the Elastic Stack

Mlockall: what happens if no memory available?

Elastic Stack Elasticsearch

Abid_Hussain (Abid Hussain) June 25, 2015, 10:27am 5

Thanks for clarification.

Topic		Replies	Views
Trouble understanding mlockall behaviour Elasticsearch	6	710	July 6, 2017
Mlockall vs ES_HEAP_SIZE Elasticsearch	2	654	July 5, 2017
Java process been swapped with mlockall True Elasticsearch	1	545	October 26, 2017
What is use of setting mlockall to true? Elasticsearch	3	878	July 5, 2017
Mlockall and mmapfs store type clarification Elasticsearch	2	632	July 6, 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.

Mlockall: what happens if no memory available?

Related topics