# Memlock settings not taking effect?

**URL:** <https://discuss.elastic.co/t/memlock-settings-not-taking-effect/62209>\
**Category:** Elasticsearch\
**Created:** [October 4, 2016, 7:01pm UTC](https://discuss.elastic.co/t/memlock-settings-not-taking-effect/62209 "2016-10-04T19:01:23Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ZillaG](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zillag/32/10505_2.png) [@ZillaG](https://discuss.elastic.co/u/ZillaG)\
**Post date:** [October 4, 2016, 7:01pm UTC](https://discuss.elastic.co/t/memlock-settings-not-taking-effect/62209/1 "2016-10-04T19:01:23Z")

</div>

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 /etc/security/limits.conf, for example:
        # allow user 'elasticsearch' mlockall
        elasticsearch soft memlock unlimited
        elasticsearch hard memlock unlimited
```

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 6, 2016, 7:34am UTC](https://discuss.elastic.co/t/memlock-settings-not-taking-effect/62209/2 "2016-10-06T07:34:03Z")

</div>

What OS?

---

<div class="post-metadata">

**Author:** ![ZillaG](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zillag/32/10505_2.png) [@ZillaG](https://discuss.elastic.co/u/ZillaG)\
**Post date:** [October 6, 2016, 1:29pm UTC](https://discuss.elastic.co/t/memlock-settings-not-taking-effect/62209/3 "2016-10-06T13:29:20Z")

</div>

CentOS 7.2. I upgraded to ES v2.4.1 now, and still see it.

---

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\
**Post date:** [October 6, 2016, 7:23pm UTC](https://discuss.elastic.co/t/memlock-settings-not-taking-effect/62209/4 "2016-10-06T19:23:38Z")

</div>

Note that the setting was renamed in 2.4

bootstrap.memory\_lock: true

---

<div class="post-metadata">

**Author:** ![ZillaG](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zillag/32/10505_2.png) [@ZillaG](https://discuss.elastic.co/u/ZillaG)\
**Post date:** [October 6, 2016, 7:25pm UTC](https://discuss.elastic.co/t/memlock-settings-not-taking-effect/62209/5 "2016-10-06T19:25:24Z")

</div>

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

---

<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:** [July 5, 2017, 10:14pm UTC](https://discuss.elastic.co/t/memlock-settings-not-taking-effect/62209/6 "2017-07-05T22:14:12Z")

</div>