# RED status in elastic search indices

**URL:** https://discuss.elastic.co/t/red-status-in-elastic-search-indices/142200
**Category:** Elasticsearch
**Created:** [July 30, 2018, 2:31pm UTC](https://discuss.elastic.co/t/red-status-in-elastic-search-indices/142200 "2018-07-30T14:31:38Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![rmanju2020](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rmanju2020/32/44560_2.png) [@rmanju2020](https://discuss.elastic.co/u/rmanju2020)
#### Post date: [July 30, 2018, 2:31pm UTC](https://discuss.elastic.co/t/red-status-in-elastic-search-indices/142200/1 "2018-07-30T14:31:38Z")

</div>

I have observed that  
1)whenever a RED status happen on one indices, the next all creating indices will be in RED status.  
2)The UNASSIGNED shards of indices doesn't have data.Hence these indices will never become Yellow or Green status.

I referred [Elastic Search is always status red when I restart with no data in index](https://discuss.elastic.co/t/elastic-search-is-always-status-red-when-i-restart-with-no-data-in-index/14991/4) and other threads but nothing is solved my issue.Kindly suggest.

ES version 1.6.0

No error in ES logs.Number of shards:3 Replica:0 and allocated memory 6GB  
HW: 16 GB RAM,8 cores and windows 2008 R2 and 1 TB hard disk

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [July 30, 2018, 2:46pm UTC](https://discuss.elastic.co/t/red-status-in-elastic-search-indices/142200/2 "2018-07-30T14:46:31Z")

</div>

> ES version 1.6.0

Is it a typo?

---

<div class="post-metadata">

### Author: ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [July 30, 2018, 3:02pm UTC](https://discuss.elastic.co/t/red-status-in-elastic-search-indices/142200/3 "2018-07-30T15:02:09Z")

</div>

I thought we established that you probably have too many shards and needed to do something about it in [this thread](https://discuss.elastic.co/t/logstash-throwing-error-503/142163). Have you already addressed that?

---

<div class="post-metadata">

### Author: ![rmanju2020](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rmanju2020/32/44560_2.png) [@rmanju2020](https://discuss.elastic.co/u/rmanju2020)
#### Post date: [July 31, 2018, 6:34am UTC](https://discuss.elastic.co/t/red-status-in-elastic-search-indices/142200/4 "2018-07-31T06:34:16Z")

</div>

It mean elastic search version 1.6.0

---

<div class="post-metadata">

### Author: ![rmanju2020](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rmanju2020/32/44560_2.png) [@rmanju2020](https://discuss.elastic.co/u/rmanju2020)
#### Post date: [July 31, 2018, 6:37am UTC](https://discuss.elastic.co/t/red-status-in-elastic-search-indices/142200/5 "2018-07-31T06:37:42Z")

</div>

Yes ,Its been address half the way,means deleted index beyond 3 months older + Reduced shards /node to 1 .It saved a lot of space and reduced load.  
The Reindex is under way..  
But i have posted question here considering different issue and need to address in other way,Any way will see once all this is done  
Thanks Christian\_Dahlqvist

---

<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: [August 28, 2018, 6:37am UTC](https://discuss.elastic.co/t/red-status-in-elastic-search-indices/142200/6 "2018-08-28T06:37:44Z")

</div>

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