Hi all I have following situation. We use 20 node cluster with replication 1. We have 5 masters and minimal master count is set to 3. When cluster is initializing, relocating_shards or creating new indice master node utilize 1 CPU core to 100% and during that time other nodes can not join cluste…

ES client nor node can not join cluster while it performs maintenance or shard relocation

Topic		Replies	Views
Replica stuck in relocation, high cpu usage Elasticsearch	11	741	July 6, 2017
ElasticSearch cannot join cluster Elasticsearch	7	620	July 6, 2017
Failed to connect to busy master Elasticsearch	18	2070	October 29, 2018
Elasticsearch nodes continually disconneting/reconnecting. Resulting in very high number of unassigned shards Elasticsearch	18	3136	September 3, 2020
Nodes fail to join cluster - potential split brain scenario Elasticsearch	11	588	July 6, 2017