# Confirming exact definition of "red" and "yellow" for index status for a multi data node cluster

**URL:** <https://discuss.elastic.co/t/confirming-exact-definition-of-red-and-yellow-for-index-status-for-a-multi-data-node-cluster/154933>\
**Category:** Elasticsearch\
**Created:** [October 31, 2018, 9:50pm UTC](https://discuss.elastic.co/t/confirming-exact-definition-of-red-and-yellow-for-index-status-for-a-multi-data-node-cluster/154933 "2018-10-31T21:50:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![casieowen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/casieowen/32/8734_2.png) [@casieowen](https://discuss.elastic.co/u/casieowen)\
**Post date:** [October 31, 2018, 9:50pm UTC](https://discuss.elastic.co/t/confirming-exact-definition-of-red-and-yellow-for-index-status-for-a-multi-data-node-cluster/154933/1 "2018-10-31T21:50:59Z")

</div>

Hi!

Is this correct:

RE: the GET \_cat/indices? api: if it returns red for an index (on a multi data node cluster), it means that at least one primary shard and all its replicas are unavailable, and if it returns yellow, at least one of the replica shards is unavailable?

Thanks!

---

<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:** [November 1, 2018, 1:11am UTC](https://discuss.elastic.co/t/confirming-exact-definition-of-red-and-yellow-for-index-status-for-a-multi-data-node-cluster/154933/2 "2018-11-01T01:11:41Z")

</div>

Red is one primary shard not available. Replicas are not considered.  
A cluster can have a primary shard unavailable but the replicas may all be ok, eg if it's working on promoting a replica shard to a primary.

---

<div class="post-metadata">

**Author:** ![casieowen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/casieowen/32/8734_2.png) [@casieowen](https://discuss.elastic.co/u/casieowen)\
**Post date:** [November 2, 2018, 12:55am UTC](https://discuss.elastic.co/t/confirming-exact-definition-of-red-and-yellow-for-index-status-for-a-multi-data-node-cluster/154933/3 "2018-11-02T00:55:47Z")

</div>

OK, so from a data availability perspective, this api isn't going to provide useful info, because even x number of primary shard(s) is/are unavailable, the replicas may be fine. Is that correct? Probably more useful to track document count and/or simply look for data during specified time buckets, etc.? Also, thanks!

---

<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:** [November 2, 2018, 2:33am UTC](https://discuss.elastic.co/t/confirming-exact-definition-of-red-and-yellow-for-index-status-for-a-multi-data-node-cluster/154933/4 "2018-11-02T02:33:41Z")

</div>

It depends on what you are looking for I guess.

---

<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:** [November 30, 2018, 2:33am UTC](https://discuss.elastic.co/t/confirming-exact-definition-of-red-and-yellow-for-index-status-for-a-multi-data-node-cluster/154933/5 "2018-11-30T02:33:44Z")

</div>

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