Multiple Replica shards are stuck in initialisation phase because there seems to be a mismatch in the Shard status. I am seeing multiple messages of this type [indices.recovery ] [node-24] delaying recovery of [index][1] as it is not listed as initializing on the target node [][kt7d733XQ_K…

Shards stuck in INITIALIZATION due to mismatch in State on targetnode

Christian_Dahlqvist (Christian Dahlqvist) October 31, 2019, 6:29am 2

This looks quite unusual. Is this on the same Elasticsearch 5.6 cluster where you have modified the leader election and shard allocation logic?

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.