Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: vm.max_map_count is not set to 262144 when using Systemd service #621

Open
nareen2 opened this issue Nov 1, 2017 · 1 comment
Open
Labels
Bug Something isn't working

Comments

@nareen2
Copy link

nareen2 commented Nov 1, 2017

Hi,

I used this cookbook to deploy 3-node Elasticsearch cluster[Version 5.6.3] on Redhat platform. I've defined node['elasticsearch']['configure']['max_map_count'] to 262144 and used Systemd to configure the service, but the service is failing with:

[1] bootstrap checks failed
[1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144].

I had to manually run `sysctl to increase that. Can you please take a look and let me know if I miss some configuration to set that value?

@martinb3
Copy link
Contributor

martinb3 commented Nov 2, 2017

Hi there -- I believe systemd doesn't respect the settings in /etc/sysconfig/elasticsearch or /etc/default/elasticsearch. You're welcome to follow these instructions to override settings there.

Eventually Elasticsearch is going to stop supporting as many environment variables for these sorts of settings, which will mean that we'll probably have to take an alternate approach.

@martinb3 martinb3 added the Bug Something isn't working label Nov 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants