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

Approaches for ulimit setting #425

Closed
davidski opened this issue Jan 16, 2016 · 4 comments
Closed

Approaches for ulimit setting #425

davidski opened this issue Jan 16, 2016 · 4 comments

Comments

@davidski
Copy link

With #319 now in play, is there a suggested way to properly adjust ulimits to useful values? Working towards using the 2.x branches of both this cookbook and ES in general, I've found my ES nodes on AWS Linux are coming up with only 30K nofiles available while older ES 1.x/coobook 0.13.x nodes have 64k courtesy of the 10-cookbook.conf file.

Mocking up a new template for /etc/security/limit.d is easy enough, but I don't want to go reinventing a bad wheel if that's been determined to be a bad practice.

@martinb3
Copy link
Contributor

@martinb3 martinb3 added Bug Something isn't working question and removed Bug Something isn't working labels Jan 16, 2016
@davidski
Copy link
Author

Thanks for the detailed response, @martinb3! That was super helpful. In testing, I've found that AWS Linux supplies a /etc/security/limits.d/default.conf file with a nofile setting of 30,000. This appears to block the ability of the init script to override this to a higher volume. This default doesn't appear on either Centos 6.4 or Centos 7.1, so I presume this is an AWS specific tweak.

Is having this limit set to the package desired default of 65,535 on AWS Linux something you'd care for this cookbook to do? Again, it's easy enough for me to drop a file in that directory via my cookbook leveraging the elasticsearch resources, so no offense taken if that's something you'd rather not do, though it may be worth a note in the docs for folks on this platform.

@davidski
Copy link
Author

I found the limits.d file was being dropped by an upstream cookbook and not part of the base image, so this is definitely not a problem for this cookbook. Sorry for the noise. Revoking my issue permissions for $SOME_PERIOD. 😭

@martinb3
Copy link
Contributor

It's all good! I prefer noise over silence! :D

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