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

If bootstrap.mlockall is true, MAX_LOCKED_MEMORY should be set to unlimited in elasticsearch-env.sh #266

Closed
skyshard opened this issue Dec 25, 2014 · 1 comment

Comments

@skyshard
Copy link
Contributor

as documented at http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-service.html and a few other issues

@skyshard skyshard changed the title If bootstrap.mlockall is true, MAX_LOCKED_MEMORY should be set in elasticsearch-env.sh If bootstrap.mlockall is true, MAX_LOCKED_MEMORY should be set to unlimited in elasticsearch-env.sh Dec 25, 2014
@martinb3
Copy link
Contributor

martinb3 commented Jul 7, 2015

Hello! I think we're going to use #320 to track this issue. We think we may just remove this entirely and use the init scripts provided by the elasticsearch repos, including how they customize settings like MAX_LOCKED_MEMORY.

We've re-written the cookbook using libraries that expose resources and providers, so you shouldn't have a problem manually setting MAX_LOCKED_MEMORY on the newer version; it should also be much easier to customize. Hope this helps!

@martinb3 martinb3 closed this as completed Jul 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants