# Elasticsearch status RED

**URL:** <https://discuss.elastic.co/t/elasticsearch-status-red/85685>\
**Category:** Elasticsearch\
**Created:** [May 14, 2017, 3:42pm UTC](https://discuss.elastic.co/t/elasticsearch-status-red/85685 "2017-05-14T15:42:54Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rrs](https://avatars.discourse-cdn.com/v4/letter/r/d9b06d/32.png) [@rrs](https://discuss.elastic.co/u/rrs)\
**Post date:** [May 14, 2017, 3:42pm UTC](https://discuss.elastic.co/t/elasticsearch-status-red/85685/1 "2017-05-14T15:42:55Z")

</div>

Hi All,

I am I bit confused about my Elasticsearch index. Some of the the indexes are turned into RED, while some are in Yellow status. I am suspecting the issue with unassigned\_shards. Can anyone explain me is the Elasticsearch is running fine or the issue exists with unassigned\_shards?

Thanks in advance.

"cluster\_name" : "logstash",  
"status" : "red",  
"timed\_out" : false,  
"number\_of\_nodes" : 1,  
"number\_of\_data\_nodes" : 1,  
"active\_primary\_shards" : 621,  
"active\_shards" : 621,  
"relocating\_shards" : 0,  
"initializing\_shards" : 0,  
"unassigned\_shards" : 637,  
"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" : 49.36406995230524

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 14, 2017, 8:10pm UTC](https://discuss.elastic.co/t/elasticsearch-status-red/85685/2 "2017-05-14T20:10:59Z")

</div>

You should look at `_cat/indices` to see what is unassigned.

> [@rrs](#):
>
> "number\_of\_data\_nodes" : 1,  
> "active\_primary\_shards" : 621,

That's a little high, you should look to reduce your default shard count.

---

<div class="post-metadata">

**Author:** ![rrs](https://avatars.discourse-cdn.com/v4/letter/r/d9b06d/32.png) [@rrs](https://discuss.elastic.co/u/rrs)\
**Post date:** [May 15, 2017, 6:16am UTC](https://discuss.elastic.co/t/elasticsearch-status-red/85685/3 "2017-05-15T06:16:48Z")

</div>

Thanks for update.

As per your suggestion, I checked the unassigned indices which are 8 primary and 624 replicas.

Whey should I worry when active\_primary\_shards and unassigned\_shards numbers are high? Is there any algorithm to maintain proper cluster with number of nodes based on number of both indexes(primary/replica).

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 15, 2017, 8:57am UTC](https://discuss.elastic.co/t/elasticsearch-status-red/85685/4 "2017-05-15T08:57:39Z")

</div>

> [@rrs](#):
>
> unassigned indices which are 8 primary

That is a problem and why your cluster is red. You should check your logs to see what may be causing it.

> [@rrs](#):
>
> Whey should I worry when active\_primary\_shards and unassigned\_shards numbers are high?

See [Kagillion Shards | Elasticsearch: The Definitive Guide [2.x] | Elastic](https://www.elastic.co/guide/en/elasticsearch/guide/2.x/kagillion-shards.html)

> [@rrs](#):
>
> Is there any algorithm to maintain proper cluster with number of nodes based on number of both indexes(primary/replica).

It's a mix of things, there are other threads that go into this in more detail so have a bit of a look around 🙂

---

<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:** [June 12, 2017, 9:11am UTC](https://discuss.elastic.co/t/elasticsearch-status-red/85685/5 "2017-06-12T09:11:58Z")

</div>

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