# Elasticsearch index health turned Red!

**URL:** <https://discuss.elastic.co/t/elasticsearch-index-health-turned-red/83805>\
**Category:** Elasticsearch\
**Created:** [April 27, 2017, 7:18am UTC](https://discuss.elastic.co/t/elasticsearch-index-health-turned-red/83805 "2017-04-27T07:18:39Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![Yong\_Zhang](https://avatars.discourse-cdn.com/v4/letter/y/a183cd/32.png) [@Yong\_Zhang](https://discuss.elastic.co/u/Yong_Zhang)\
**Post date:** [April 29, 2017, 2:24am UTC](https://discuss.elastic.co/t/elasticsearch-index-health-turned-red/83805/10 "2017-04-29T02:24:31Z")

</div>

I have exactly the same use case and the same issue with you.  
I'm also running es cluster in Kubernetes and using glusterfs as storage backend, my glusterfs version is 3.10.1, but have the same issue with you, here's my topic [Shard repeat to be UNASSIGNED](https://discuss.elastic.co/t/shard-repeat-to-be-unassigned/83975/3) raised just yesterday...

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-index-health-turned-red/83805)._