# MAX\_LOCKED\_MEMORY=unlimited setting in Elasticsearch 8.x

**URL:** <https://discuss.elastic.co/t/max-locked-memory-unlimited-setting-in-elasticsearch-8-x/329884>\
**Category:** Elasticsearch\
**Created:** [April 13, 2023, 5:34am UTC](https://discuss.elastic.co/t/max-locked-memory-unlimited-setting-in-elasticsearch-8-x/329884 "2023-04-13T05:34:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tomas\_Bartek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tomas_bartek/32/45776_2.png) [@Tomas\_Bartek](https://discuss.elastic.co/u/Tomas_Bartek)\
**Post date:** [April 13, 2023, 5:34am UTC](https://discuss.elastic.co/t/max-locked-memory-unlimited-setting-in-elasticsearch-8-x/329884/1 "2023-04-13T05:34:29Z")

</div>

Is `MAX_LOCKED_MEMORY=unlimited` settings in /etc/default/elasticsearch (on Ubuntu) still necessary in Elasticsearch 8.x?

It looks like settings in /etc/default/elasticsearch system configuration file is quite simplified and the commented MAX\_LOCKED\_MEMORY setting is not present like in previous Elasticsearch versions.

I still use `bootstrap.memory_lock: true` in elasticsearch.yml.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 11, 2023, 5:35am UTC](https://discuss.elastic.co/t/max-locked-memory-unlimited-setting-in-elasticsearch-8-x/329884/2 "2023-05-11T05:35:21Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.