Hi all, I am setting up Elasticsearch 3-nodes cluster with docker. This is my docker compose file: version: '2.0' services: elasticsearch: image: docker.elastic.co/elasticsearch/elasticsearch-oss:6.3.0 environment: - cluster.name=test-cluster - node.name=elastic_1 - ES_…

docker stop is too aggressive here - it tears down the node and its network interface before a new node is elected as master. The new node then tries to contact the old master, but because the old master has completely vanished the connection attempt gets no response until it times out. This is muc…

Thank you, @DavidTurner When using docker restart, re-election works fine.

Discuss the Elastic Stack

'timed out waiting for all nodes to process published state' and cluster unavailability

Elastic Stack Elasticsearch

Topic		Replies	Views
Cluster instability if master leader is stopped Elasticsearch	6	4626	June 29, 2018
Can not elect master when restarting cluster from 7.3 upgrade Elasticsearch	18	6943	September 4, 2019
Failure to elect master, v7.17 Elasticsearch docker	19	940	August 6, 2023
Master election takes too long Elasticsearch	19	2087	April 18, 2019
ElasticSearch Unstable Elasticsearch	12	7182	June 6, 2018

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

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.

'timed out waiting for all nodes to process published state' and cluster unavailability

Related topics