Memlock check is incorrect in v2.3.1

Elastic Stack Elasticsearch
1

I'm still getting this in the startup logs:

[2017-11-06 20:47:12,764][WARN ][bootstrap                ] Unable to lock JVM Memory: error=12,reason=Cannot allocate memory
[2017-11-06 20:47:12,765][WARN ][bootstrap                ] This can result in part of the JVM being swapped out.
[2017-11-06 20:47:12,765][WARN ][bootstrap                ] Increase RLIMIT_MEMLOCK, soft limit: 65536, hard limit: 65536
[2017-11-06 20:47:12,765][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

despite having this:

# allow user 'elasticsearch' mlockall
elasticsearch   soft    memlock unlimited
elasticsearch   hard    memlock unlimited

in a file located: /etc/security/limits.d/elasticsearch.conf

Do I need to do something else? (eg: Help getting mlockall to work on ubuntu 14.04)

Also, we have configured vm.swappiness, but still get this warning. It'd be great if the startup check checked all available options to ensure that at least one of them is checked and didn't bother warning you if something was setup correctly...

2

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