I am working to get elastic search up and running on a docker container. Basically my AWS instance has 16 GB of RAM & 10 GB of memory.
Whenever I am trying to run the image, it gives me below error. My understanding is because due to vm.max_map_count param which is too low.
Can someone suggest me where can I find this parameter ? If it's inside the container how can I even edit this under /etc/sysctl.conf ?
URL - https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html#_linux
{"@timestamp":"2025-02-07T12:47:07.365Z", "log.level":"ERROR", "message":"node validation exception\n bootstrap checks failed.
You must address the points described in the following lines before starting Elasticsearch.
For more information see [https://www.elastic.co/guide/en/elasticsearch/reference/8.17/bootstrap-checks.html]\nbootstrap check failure of :
max virtual memory areas vm.max_map_count is too low, increase to at least ;
for more information see [https://www.elastic.co/guide/en/elasticsearch/reference/8.17/bootstrap-checks-max-map-count.html] ", "ecs.version": "1.2.0",
"service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"main","log.logger":"org.elasticsearch.bootstrap.Elasticsearch",
"elasticsearch.node.name":"592a6fd6de3b","elasticsearch.cluster.name":"docker-cluster"}
ERROR: Elasticsearch did not exit normally - check the logs at /usr/share/elasticsearch/logs/docker-cluster.log
{"@timestamp":"2025-02-07T12:47:07.372Z", "log.level": "INFO", "message":"stopping ...", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch-shutdown","log.logger":"org.elasticsearch.node.Node","elasticsearch.node.name":"592a6fd6de3b","elasticsearch.cluster.name":"docker-cluster"}
{"@timestamp":"2025-02-07T12:47:07.390Z", "log.level": "INFO", "message":"stopped", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch-shutdown","log.logger":"org.elasticsearch.node.Node","elasticsearch.node.name":"592a6fd6de3b","elasticsearch.cluster.name":"docker-cluster"}
{"@timestamp":"2025-02-07T12:47:07.390Z", "log.level": "INFO", "message":"closing ...", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch-shutdown","log.logger":"org.elasticsearch.node.Node","elasticsearch.node.name":"592a6fd6de3b","elasticsearch.cluster.name":"docker-cluster"}
{"@timestamp":"2025-02-07T12:47:07.401Z", "log.level": "INFO", "message":"closed", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch-shutdown","log.logger":"org.elasticsearch.node.Node","elasticsearch.node.name":"592a6fd6de3b","elasticsearch.cluster.name":"docker-cluster"}
{"@timestamp":"2025-02-07T12:47:07.402Z", "log.level": "INFO", "message":"Native controller process has stopped - no new native processes can be started", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"ml-cpp-log-tail-thread","log.logger":"org.elasticsearch.xpack.ml.process.NativeController","elasticsearch.node.name":"592a6fd6de3b","elasticsearch.cluster.name":"docker-cluster"}
ERROR: Elasticsearch died while starting up, with exit code 78
Thanks,
Piyush
Asked by Piyush Nikhade
(11 rep)
Feb 7, 2025, 02:09 PM
Last activity: Feb 7, 2025, 02:14 PM
Last activity: Feb 7, 2025, 02:14 PM