# Memory Lock Setting Fails Bootstrap ES 6.1.1 **URL:** \ **Category:** Elasticsearch\ **Created:** [January 30, 2018, 10:10pm UTC](https://discuss.elastic.co/t/memory-lock-setting-fails-bootstrap-es-6-1-1/117709 "2018-01-30T22:10:47Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![wrinehart](https://avatars.discourse-cdn.com/v4/letter/w/ba9def/32.png) [@wrinehart](https://discuss.elastic.co/u/wrinehart)\ **Post date:** [January 30, 2018, 10:10pm UTC](https://discuss.elastic.co/t/memory-lock-setting-fails-bootstrap-es-6-1-1/117709/1 "2018-01-30T22:10:47Z")
Howdy, I am having issues getting 'bootstrap.memory\_lock: true' working with an ES version 6.1.1 cluster. `[2018-01-30T15:52:39,313][WARN][o.e.b.JNANatives] Unable to lock JVM Memory: error=12, reason=Cannot allocate memory [2018-01-30T15:52:39,317][WARN][o.e.b.JNANatives] This can result in part of the JVM being swapped out. [2018-01-30T15:52:39,318][WARN][o.e.b.JNANatives] Increase RLIMIT_MEMLOCK, soft limit: 4294967296, hard limit: 4294967296 [2018-01-30T15:52:39,318][WARN][o.e.b.JNANatives] These can be adjusted by modifying /etc/security/limits.conf, for example: # allow user 'elasticsearch' mlockall elasticsearch soft memlock unlimited elasticsearch hard memlock unlimited` I have those settings in my limits.conf file. Also, my environment has multiple clusters on each node. This particular server has pre-version 5.x clusters that have mlock configured and it works fine for them. Any help would be appreciated. Thanks -Walt ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 27, 2018, 10:11pm UTC](https://discuss.elastic.co/t/memory-lock-setting-fails-bootstrap-es-6-1-1/117709/2 "2018-02-27T22:11:40Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.