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

max file descriptors for elasticsearch process is too low #140

Closed
bitgandtter opened this issue Nov 18, 2016 · 3 comments
Closed

max file descriptors for elasticsearch process is too low #140

bitgandtter opened this issue Nov 18, 2016 · 3 comments

Comments

@bitgandtter
Copy link

Using Ubuntu 16.10
Docker 1.12.3
Docker Composer 1.8
Elastic latest tag

docker-compose.yml

elastic:
image: elasticsearch
environment:
- ES_JAVA_OPTS=-Xmx2g -Xms2g

getting on logs

elastic_1 | ERROR: bootstrap checks failed
elastic_1 | max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]
elastic_1 | [2016-11-18T17:48:17,058][INFO ][o.e.n.Node ] [HK_OIan] stopping ...

Any idea, thanks

@yosifkit
Copy link
Member

That looks like the vm.max_map_count issue that was part of #98. We added some info to the docs on how to fix it:

Note: since 5.0, Elasticsearch only listens on localhost by default, so this image sets network.host to 0.0.0.0 (given that localhost is not terribly useful in the Docker context).

As a result, Elasticsearch is more strict about the bootstrap checks that it performs, especially when checking the value of vm.max_map_count which is not namespaced and thus must be set to an acceptable value on the host (as opposed to simply using --sysctl on docker run).

- https://github.com/docker-library/docs/tree/master/elasticsearch#host-setup

@bitgandtter
Copy link
Author

bitgandtter commented Nov 18, 2016

I follow the doc and i fix that config as mention for vm.max_map_count but on this case was for ulimits. i fix it with following config on my docker-compose.yml

ulimits:
    nofile:
       soft: 65536
       hard: 65536

@ralyodio

This comment has been minimized.

@docker-library docker-library locked as resolved and limited conversation to collaborators Jul 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants