-
Notifications
You must be signed in to change notification settings - Fork 192
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
Important System Configuration #21
Comments
Hey @nautilus28 thanks for addressing these issues. Would these need to be configured before adding the host or after running the second playbook? |
@mbrost I think they should be done by using different tasks in specific roles of elasticsearch deployment. |
I haven't forgotten about this, I am finding time here and there to solve any open issues or RFE that people open (thanks for opening this!). I see this sort of enhancement check becoming more important as the 5.x series has become much more demanding - people running this in a VM really need at least 6-8G of memory now for example or things time out. I don't have an ETA but hope to have more time soon to implement this. |
@sadsfae Would the changes here be beneficial for m4.large OR m4.xlarge EC2 instance within AWS as well?.. |
@anash28 These changes are recommended by Elastic and should be implemented in any instance. The issue, primarily, is the JVM running out of memory and crashing your shards. |
The following settings must be addressed before going to production mode:
https://www.elastic.co/guide/en/elasticsearch/reference/current/system-config.html
I would love to have these configuration in the scripts.
Thanks for this amazing setup.
Canh
The text was updated successfully, but these errors were encountered: