Skip to content
This repository has been archived by the owner on Nov 7, 2018. It is now read-only.

Unable to set MEMORY_LOCK to true #229

Open
rewt opened this issue Sep 13, 2018 · 1 comment
Open

Unable to set MEMORY_LOCK to true #229

rewt opened this issue Sep 13, 2018 · 1 comment

Comments

@rewt
Copy link

rewt commented Sep 13, 2018

sh: error setting limit: Operation not permitted [2018-09-13T20:29:34,587][WARN ][o.e.b.JNANatives ] Unable to lock JVM Memory: error=12, reason=Out of memory [2018-09-13T20:29:34,589][WARN ][o.e.b.JNANatives ] This can result in part of the JVM being swapped out. [2018-09-13T20:29:34,589][WARN ][o.e.b.JNANatives ] Increase RLIMIT_MEMLOCK, soft limit: 65536, hard limit: 65536 [2018-09-13T20:29:34,589][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 found resolution on docker repo, could you please implement in this image as well?

@rewt
Copy link
Author

rewt commented Sep 13, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant