# Reason behind shards being in UNASSIGNED state

**URL:** <https://discuss.elastic.co/t/reason-behind-shards-being-in-unassigned-state/33678>\
**Category:** Elasticsearch\
**Created:** [November 3, 2015, 9:59pm UTC](https://discuss.elastic.co/t/reason-behind-shards-being-in-unassigned-state/33678 "2015-11-03T21:59:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pradeep\_Gowda](https://avatars.discourse-cdn.com/v4/letter/p/ebca7d/32.png) [@Pradeep\_Gowda](https://discuss.elastic.co/u/Pradeep_Gowda)\
**Post date:** [November 3, 2015, 9:59pm UTC](https://discuss.elastic.co/t/reason-behind-shards-being-in-unassigned-state/33678/1 "2015-11-03T21:59:51Z")

</div>

Hi All,

I have come across a scenario where when I bring up the node, couple of index goes to red state and their primary shards remains unassigned. I was wondering what are the reasons behind primary shards being in unassigned state. Can someone please explain me about this?

Regards,

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:40pm UTC](https://discuss.elastic.co/t/reason-behind-shards-being-in-unassigned-state/33678/2 "2017-07-05T23:40:47Z")

</div>