# Shards stuck in INITIALIZATION due to mismatch in State on targetnode
**URL:** https://discuss.elastic.co/t/shards-stuck-in-initialization-due-to-mismatch-in-state-on-targetnode/205939
**Category:** Elasticsearch
**Created:** [October 30, 2019, 7:29pm UTC](https://discuss.elastic.co/t/shards-stuck-in-initialization-due-to-mismatch-in-state-on-targetnode/205939 "2019-10-30T19:29:43Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@UDixit](https://discuss.elastic.co/u/UDixit)
#### Post date: [October 30, 2019, 7:29pm UTC](https://discuss.elastic.co/t/shards-stuck-in-initialization-due-to-mismatch-in-state-on-targetnode/205939/1 "2019-10-30T19:29:43Z")
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.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [October 31, 2019, 6:29am UTC](https://discuss.elastic.co/t/shards-stuck-in-initialization-due-to-mismatch-in-state-on-targetnode/205939/2 "2019-10-31T06:29:43Z")
This looks quite unusual. Is this on [the same Elasticsearch 5.6 cluster where you have modified the leader election and shard allocation logic](https://discuss.elastic.co/t/es5-6-unassigned-shards-due-to-dangling-index-imported/204739)?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 28, 2019, 6:29am UTC](https://discuss.elastic.co/t/shards-stuck-in-initialization-due-to-mismatch-in-state-on-targetnode/205939/3 "2019-11-28T06:29:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.