# 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:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@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")

</div>

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)?

---

_[View the full topic](https://discuss.elastic.co/t/shards-stuck-in-initialization-due-to-mismatch-in-state-on-targetnode/205939)._