# Cluster goes yellow abruptly

**URL:** <https://discuss.elastic.co/t/cluster-goes-yellow-abruptly/231669>\
**Category:** Elasticsearch\
**Created:** [May 8, 2020, 7:34am UTC](https://discuss.elastic.co/t/cluster-goes-yellow-abruptly/231669 "2020-05-08T07:34:43Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Faiz\_Ahmed\_Mushtak\_H](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/faiz_ahmed_mushtak_h/32/47387_2.png) [@Faiz\_Ahmed\_Mushtak\_H](https://discuss.elastic.co/u/Faiz_Ahmed_Mushtak_H)\
**Post date:** [May 11, 2020, 5:20am UTC](https://discuss.elastic.co/t/cluster-goes-yellow-abruptly/231669/3 "2020-05-11T05:20:11Z")

</div>

@warkolm i think its a duplicate of [Shards getting marked as stale frequently causing cluster to go yellow](https://discuss.elastic.co/t/shards-getting-marked-as-stale-frequently-causing-cluster-to-go-yellow/231835)

I have been able to correlate it with the time when we are indexing / updating huge documents around 5-10mb. In GC logs I've been seeing humongous allocations

[https://github.com/elastic/elasticsearch/pull/46169](https://github.com/elastic/elasticsearch/pull/46169) is taken care of but the IHOP is still adaptive. So isn't it possible that `InitiatingHeapOccupancyPercent` may grow back to 70% and we face the same issue again?

---

_[View the full topic](https://discuss.elastic.co/t/cluster-goes-yellow-abruptly/231669)._