Skip to content

ES 5.1.1 alpine cannot lock memory #154

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

Closed
jalberto opened this issue Jan 12, 2017 · 3 comments
Closed

ES 5.1.1 alpine cannot lock memory #154

jalberto opened this issue Jan 12, 2017 · 3 comments

Comments

@jalberto
Copy link

jalberto commented Jan 12, 2017

environment:                                                                                                                                          
  ES_JAVA_OPTS: "-Xms14g -Xmx14g"                                                                                                                     
  command: elasticsearch -Ecluster.name=vles -Ediscovery.zen.ping.unicast.hosts=es -Enode.master=true -Enode.data=true -        Enode.ingest=false -Ebootstrap.memory_lock=true

error:

[2017-01-12T10:20:09,941][WARN ][o.e.b.JNANatives         ] Unable to lock JVM Memory: error=12, reason=Out of memory
[2017-01-12T10:20:09,944][WARN ][o.e.b.JNANatives         ] This can result in part of the JVM being swapped out.
[2017-01-12T10:20:09,944][WARN ][o.e.b.JNANatives         ] Increase RLIMIT_MEMLOCK, soft limit: 65536, hard limit: 65536
[2017-01-12T10:20:09,944][WARN ][o.e.b.JNANatives         ] These can be adjusted by modifying /etc/security/limits.conf, for example: 
        # allow user 'elasticsearch' mlockall
        elasticsearch soft memlock unlimited
        elasticsearch hard memlock unlimited
[...]
ERROR: bootstrap checks failed
memory locking requested for elasticsearch process but memory is not locked

probably that configuration is missing in the alpine base image?

@jalberto
Copy link
Author

This same config was working on 5.0-alpine

@yosifkit
Copy link
Member

reason=Out of memory

You may need to change your limits or see what else on that server is using up your memory.

@tianon
Copy link
Member

tianon commented Oct 4, 2017

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.

This image has been deprecated in favor of the official elasticsearch image provided and maintained by elastic.co. The upstream images are available to pull via docker.elastic.co/elasticsearch/elasticsearch:[version] like 5.4.2. The images found here will receive no further updates once the 5.6.0 release is available upstream. Please adjust your usage accordingly.

Elastic provides open-source support for Elasticsearch via the elastic/elasticsearch GitHub repository and the Docker image via the elastic/elasticsearch-docker GitHub repository, as well as community support via its forums.

Thanks!

@tianon tianon closed this as completed Oct 4, 2017
1gtm pushed a commit to appscode-images/elasticsearch that referenced this issue Feb 14, 2024
This commit was created by the elastic-dockerfiles-publisher.
1gtm pushed a commit to appscode-images/elasticsearch that referenced this issue Feb 14, 2024
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

3 participants