# Primary shard is not active or isn't assigned is a known node

**URL:** <https://discuss.elastic.co/t/primary-shard-is-not-active-or-isnt-assigned-is-a-known-node/63182>\
**Category:** Elasticsearch\
**Created:** [October 17, 2016, 10:36am UTC](https://discuss.elastic.co/t/primary-shard-is-not-active-or-isnt-assigned-is-a-known-node/63182 "2016-10-17T10:36:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Den\_Barik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/den_barik/32/12536_2.png) [@Den\_Barik](https://discuss.elastic.co/u/Den_Barik)\
**Post date:** [October 17, 2016, 10:36am UTC](https://discuss.elastic.co/t/primary-shard-is-not-active-or-isnt-assigned-is-a-known-node/63182/1 "2016-10-17T10:36:54Z")

</div>

I use elasticsearch ver. 1.4.4 with FOS Elastica Bundle.  
On reindex data see Primary shard is not active or isn't assigned is a known node error.  
Find only this advice

> <https://stackoverflow.com/questions/27547091/primary-shard-is-not-active-or-isnt-assigned-is-a-known-node>

  
but my disk is full on 76% not 85%.  
So what a problem?  
Help me, please

---

<div class="post-metadata">

**Author:** ![Balaji.pudur](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@Balaji.pudur](https://discuss.elastic.co/u/Balaji.pudur)\
**Post date:** [April 11, 2017, 12:56pm UTC](https://discuss.elastic.co/t/primary-shard-is-not-active-or-isnt-assigned-is-a-known-node/63182/2 "2017-04-11T12:56:38Z")

</div>

> [@Den\_Barik](#):
>
> So what a problem?Help me, please

Hi ,

I am facing same issue. Please suggest me if you found fix to this issue.

Thanks  
Balaji

---

<div class="post-metadata">

**Author:** ![Balaji.pudur](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@Balaji.pudur](https://discuss.elastic.co/u/Balaji.pudur)\
**Post date:** [April 11, 2017, 7:55pm UTC](https://discuss.elastic.co/t/primary-shard-is-not-active-or-isnt-assigned-is-a-known-node/63182/3 "2017-04-11T19:55:41Z")

</div>

The issue got resolved after  
cluster.routing.allocation configured in elasticsearch.yml.

cluster.routing.allocation.disk.threshold\_enabled: false  
cluster.routing.allocation.disk.watermark.low: 500mb  
cluster.routing.allocation.disk.watermark.high: 600mb  
cluster.info.update.interval: 1m

---

<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, 10:01pm UTC](https://discuss.elastic.co/t/primary-shard-is-not-active-or-isnt-assigned-is-a-known-node/63182/4 "2017-07-05T22:01:17Z")

</div>