Shards stuck in INITIALIZATION due to mismatch in State on targetnode

Elastic Stack Elasticsearch
1

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_KBnOlIzWpyyw][zkrv-20][inet[/.128.17:9300]]. known shards state is [STARTED]

How can I force the current cluster state on the node so that it accepts the shard in Initializing state.

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?

3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.