two instance of Elasticsearch are failing to start
any clues why it says unexpected exit..
cmn-es:
container_name: app-cmn-es
environment:
ELASTIC_PASSWORD: changeme
ELASTIC_USERNAME: elastic
bootstrap.memory_lock: "true"
discovery.type: single-node
http.port: "19200"
node.name: app-cmn-es
xpack.security.enabled: "true"
xpack.security.http.ssl.enabled: "false"
hostname: cmn-es
healthcheck:
test:
- CMD-SHELL
- curl -s http://cmn-es:19200//_cat/health -u elastic:changeme | grep -E 'green|100%' || echo 'Health check failed'
timeout: 10s
interval: 15s
retries: 5
start_period: 30s
image: elasticsearch:8.13.4
networks:
es-lan-app: null
ports:
- mode: ingress
target: 19200
published: "19200"
protocol: tcp
volumes:
- type: bind
source: c:/temp/junk2/app-cmn-es/data
target: /usr/share/es/data
bind:
create_host_path: true
this is one defination
cmn-es:
container_name: esn-auto-cmn-es
environment:
ELASTIC_PASSWORD: changeme
ELASTIC_USERNAME: elastic
bootstrap.memory_lock: "true"
discovery.type: single-node
http.port: "9200"
node.name: esn-auto-cmn-es
xpack.security.enabled: "true"
xpack.security.http.ssl.enabled: "false"
hostname: cmn-es
healthcheck:
test:
- CMD-SHELL
- curl -s http://cmn-es:9200//_cat/health -u elastic:changeme | grep -E 'green|100%' || echo 'Health check failed'
timeout: 10s
interval: 15s
retries: 5
start_period: 30s
image: elasticsearch:8.13.4
networks:
es-lan-esn-auto: null
ports:
- mode: ingress
target: 9200
published: "9200"
protocol: tcp
volumes:
- type: bind
source: c:/temp/junk2/esn-auto-cmn-es/data
target: /usr/share/es/data
bind:
create_host_path: true
this is another defination
Got the solution.. this was a memory issue
- ES_JAVA_OPTS=-Xms750m -Xmx750m
this has taken care
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.