# Unassigned shard issue

**URL:** <https://discuss.elastic.co/t/unassigned-shard-issue/43360>\
**Category:** Elasticsearch\
**Created:** [March 3, 2016, 10:02am UTC](https://discuss.elastic.co/t/unassigned-shard-issue/43360 "2016-03-03T10:02:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![adrianolimit](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrianolimit/32/11930_2.png) [@adrianolimit](https://discuss.elastic.co/u/adrianolimit)\
**Post date:** [March 3, 2016, 10:02am UTC](https://discuss.elastic.co/t/unassigned-shard-issue/43360/1 "2016-03-03T10:02:20Z")

</div>

Hello Elasticusers,

I have a big problem since yesterday, when I create a new index in Elasticsearch (3 shards and 1 replica), it is unassigned and it stays in this state...

![](https://us1.discourse-cdn.com/elastic/original/2X/1/12f06337710b994e5dbb239b621acf4672352926.png)

I never has had this type of issue before... Does somebody know what is the problem ?

This is more information about my Elasticsearch cluster :

![](https://us1.discourse-cdn.com/elastic/original/2X/5/5474a8c837f2064eb07e0ce41c9cc46432282971.png)

I have 2 nodes, one node has 7gb of memory and the other node has 4gb of memory.

Hope you could help me, I'm losing my mind with this problem.

---

<div class="post-metadata">

**Author:** ![jimczi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jimczi/32/47985_2.png) [@jimczi](https://discuss.elastic.co/u/jimczi)\
**Post date:** [March 3, 2016, 11:41am UTC](https://discuss.elastic.co/t/unassigned-shard-issue/43360/2 "2016-03-03T11:41:23Z")

</div>

Which version of elasticsearch are you using. Did you check the logs of your cluster ? 240 indices and 728 shards seems huge for a 2 nodes setup, could you explain why you need so many indices/shards ?

---

<div class="post-metadata">

**Author:** ![adrianolimit](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrianolimit/32/11930_2.png) [@adrianolimit](https://discuss.elastic.co/u/adrianolimit)\
**Post date:** [March 3, 2016, 3:16pm UTC](https://discuss.elastic.co/t/unassigned-shard-issue/43360/3 "2016-03-03T15:16:07Z")

</div>

I'm using Elasticsearch 2.2.0, I checked the logs files and I didn't see something special. I have 240 indices because some indices by day in order to see the date evolution. Do you have any idea?

---

<div class="post-metadata">

**Author:** ![adrianolimit](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrianolimit/32/11930_2.png) [@adrianolimit](https://discuss.elastic.co/u/adrianolimit)\
**Post date:** [March 4, 2016, 10:45am UTC](https://discuss.elastic.co/t/unassigned-shard-issue/43360/4 "2016-03-04T10:45:07Z")

</div>

I have found an interesting log :

[WARN][indices.memory] failed to set shard [my\_index] index buffer to [31mb]  
org.apache.lucene.store.AlreadyClosedException: translog [1] is already closed

---

<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:11pm UTC](https://discuss.elastic.co/t/unassigned-shard-issue/43360/5 "2017-07-05T23:11:18Z")

</div>


