# How to resolve the UNASSIGNED index

**URL:** <https://discuss.elastic.co/t/how-to-resolve-the-unassigned-index/76113>\
**Category:** Elasticsearch\
**Created:** [February 22, 2017, 9:35pm UTC](https://discuss.elastic.co/t/how-to-resolve-the-unassigned-index/76113 "2017-02-22T21:35:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![spraveenjd](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@spraveenjd](https://discuss.elastic.co/u/spraveenjd)\
**Post date:** [February 22, 2017, 9:35pm UTC](https://discuss.elastic.co/t/how-to-resolve-the-unassigned-index/76113/1 "2017-02-22T21:35:11Z")

</div>

I have 3 node cluster. had a configuration in elastic search yml as below  
index.number\_of\_replicas: 2 (1 is primary, 2 replica so totally 3 node cluster)  
index.number\_of\_shards: 3 (3 node cluster)

But Still my cluster is in RED, with unassigned index

"status" : "red",  
"timed\_out" : false,  
"number\_of\_nodes" : 3,  
"number\_of\_data\_nodes" : 3,  
"active\_primary\_shards" : 168,  
"active\_shards" : 266,  
"relocating\_shards" : 0,  
"initializing\_shards" : 2,  
"unassigned\_shards" : 13,  
"delayed\_unassigned\_shards" : 0,  
"number\_of\_pending\_tasks" : 0,  
"number\_of\_in\_flight\_fetch" : 0,  
"task\_max\_waiting\_in\_queue\_millis" : 0,  
"active\_shards\_percent\_as\_number" : 94.66192170818505

Please help me to resolve this.

Did I missing any other config

---

<div class="post-metadata">

**Author:** ![jkuang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jkuang/32/72637_2.png) [@jkuang](https://discuss.elastic.co/u/jkuang)\
**Post date:** [February 22, 2017, 10:24pm UTC](https://discuss.elastic.co/t/how-to-resolve-the-unassigned-index/76113/2 "2017-02-22T22:24:25Z")

</div>

Please check the blog post below:

> **[Modern monitoring & analytics](https://www.datadoghq.com/blog/elasticsearch-unassigned-shards/)**
>
> See metrics from all of your apps, tools & services in one place with Datadog's cloud monitoring as a service solution. Try it for free.

I find it really helpful.

---

<div class="post-metadata">

**Author:** ![spraveenjd](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@spraveenjd](https://discuss.elastic.co/u/spraveenjd)\
**Post date:** [February 22, 2017, 10:31pm UTC](https://discuss.elastic.co/t/how-to-resolve-the-unassigned-index/76113/3 "2017-02-22T22:31:50Z")

</div>

sure will take look..  
How the replica and the shards are configured.  
I thought replication is to all the cluster and shards also in all the cluster.  
both should match the number of node. is this correct understanding

---

<div class="post-metadata">

**Author:** ![jkuang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jkuang/32/72637_2.png) [@jkuang](https://discuss.elastic.co/u/jkuang)\
**Post date:** [February 22, 2017, 11:56pm UTC](https://discuss.elastic.co/t/how-to-resolve-the-unassigned-index/76113/4 "2017-02-22T23:56:30Z")

</div>

ES will allocate the shards and replicas appropriately and according based on the number of nodes you have in the cluster. If it can distribute because you have more nodes it will do so.

---

<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:** [March 22, 2017, 11:57pm UTC](https://discuss.elastic.co/t/how-to-resolve-the-unassigned-index/76113/5 "2017-03-22T23:57:00Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.