-
Notifications
You must be signed in to change notification settings - Fork 343
Disable memory swapping #116
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
Comments
I also can't get this to work in a Docker container. Seems like the instructions are for everything except Alpine linux, which is what the official image is on. @Doweig ever find any solutions for this? |
Nope |
Stuck on the same issue. Anybody ? |
+1 |
Only the third of the suggested fixes is possible within a container -- the first two need to be completed on the container host instead. As for changing the default options, we try to stick as close as possible to what upstream provides. |
someone find any solutions for this? |
This image is officially deprecated in favor of upstream's images (see https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html). For more information, please see #160, docker-library/docs#842, and docker-library/docs#945.
Thanks! |
Uh oh!
There was an error while loading. Please reload this page.
Hello guys,
I am currently trying to optimize Elasticsearch in production.
I have noticed that is it recommended to disable memory swapping in production and the official documentation is giving 3 ways to accomplish that:
https://www.elastic.co/guide/en/elasticsearch/guide/current/heap-sizing.html#_swapping_is_the_death_of_performance
1-
sudo swapoff -a
+ edit/etc/fstab
2- Change the
sysctl
value,vm.swappiness = 1
3- Change java options by editing
elasticsearch.yml
,bootstrap.mlockall: true
Inside the docker image however, none of there 3 ways have been implemented
Is it something that should be handled on docker level or on the host level ?
Thank you in advance guys!
The text was updated successfully, but these errors were encountered: