Open ediewoelfle opened 5 years ago
adding discovery.type
= single-node
to the environment variables fixes the issue, but undesirable.
@ediewoelfle Thank you. You save my day 👍
My environment is initially equipped with ES cluster, and one node always exits, and then reports exit with 137
, the query is a memory problem.
Therefore, I switched to a single ES node and modified my docker-compose.yml
configuration. I modified the environment configuration as discovery.type=single-node
, and found error report elastic_es01_1 exited with code 1
!
My fix: Remove the previous volume binding directory directly(ES Cluster), and run docker again and everything is ok!
My docker-compose.yml:
version: "3.7"
services:
es01:
image: elasticsearch:7.4.2
environment:
- node.name=es01
- cluster.name=es-docker-cluster
- discovery.type=single-node
volumes:
- /data/elastic/data01:/usr/share/elasticsearch/data
networks:
- elastic
ports:
- 9200:9200
- 9300:9300
networks:
elastic:
driver: bridge
Looks like you are entered into production mode after explicit network.host: 0.0.0.0
and then, according to your logs, it fails on bootstrap checks :
[1]: the default discovery settings are unsuitable for production use; at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_nodes] must be configured
It is required to do proper configuration setup since 7.0+ version.
You need to specify at least one of discovery.seed_hosts
, discovery.seed_providers
or cluster.initial_master_nodes
in $ES_HOME/config/elasticsearch.yml
Thank you
My environment is initially equipped with ES cluster, and one node always exits, and then reports
exit with 137
, the query is a memory problem.Therefore, I switched to a single ES node and modified my
docker-compose.yml
configuration. I modified the environment configuration asdiscovery.type=single-node
, and found error reportelastic_es01_1 exited with code 1
!My fix: Remove the previous volume binding directory directly(ES Cluster), and run docker again and everything is ok!
My docker-compose.yml:
version: "3.7" services: es01: image: elasticsearch:7.4.2 environment: - node.name=es01 - cluster.name=es-docker-cluster - discovery.type=single-node volumes: - /data/elastic/data01:/usr/share/elasticsearch/data networks: - elastic ports: - 9200:9200 - 9300:9300 networks: elastic: driver: bridge
This helped me
Expected behavior
Logs from a new 6.8.0 ES container:
Actual behavior
Logs from a new 7.2.0 ES container:
Information about the Issue
Every ES container above 6.8.0 fails to start.
Steps to reproduce the behavior