Recently upgraded from 0.19.12 to 0.20.5. A node went down over the weekend in my 30 node cluster. I use ES as a DB so there were constant writes while the node was down. Restarted the node and went RED. [2013-03-10 15:28:22,209][WARN ][indices.cluster ] [moloches-m13b] [stats][0] fa…

ES 0.20.5 stuck in RED after node loss OR how do I configured to avoid problems?

Topic		Replies	Views
ES Cluster Recovery and Restart Elasticsearch	3	639	July 6, 2017
Elasticsearch Node went down abruptly and lost data Elasticsearch	5	651	October 23, 2023
0.19.10 - cluster wedged, most operations failing Elasticsearch	4	491	July 6, 2017
ES Ate My Shards/Indexes Elasticsearch	13	589	July 6, 2017
Recovery from red ES node and red indices Elasticsearch	4	607	July 6, 2017

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.

ES 0.20.5 stuck in RED after node loss OR how do I configured to avoid problems?

Related topics