# Cluster Yellow - Heap size overload

**URL:** <https://discuss.elastic.co/t/cluster-yellow-heap-size-overload/248292>\
**Category:** Elasticsearch\
**Created:** [September 11, 2020, 9:30am UTC](https://discuss.elastic.co/t/cluster-yellow-heap-size-overload/248292 "2020-09-11T09:30:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Thomas74](https://avatars.discourse-cdn.com/v4/letter/t/3bc359/32.png) [@Thomas74](https://discuss.elastic.co/u/Thomas74)\
**Post date:** [September 11, 2020, 9:30am UTC](https://discuss.elastic.co/t/cluster-yellow-heap-size-overload/248292/1 "2020-09-11T09:30:05Z")

</div>

Hi,

An ILM policy had a conflict with curator last night. It wasn't working because of closed index.  
I reopen it and retry ilm policy and seems ok.

But my cluster still yellow and cannot reallocate shard because of this :

`Data too large, data for [<transport_request>] would be [30660165828/28.5gb], which is larger than the limit of [30601641984/28.5gb], real usage: [30660162168/28.5gb], new bytes reserved: [3660/3.5kb], usages [request=0/0b, fielddata=7205127741/6.7gb, in_flight_requests=3660/3.5kb, accounting=10134822598/9.4gb]]; ], allocation_status[no_attempt]]]"`

I think it is because of too hight heap size memory.

How can I reduce heap size memory ? Close indexes can reduce it ?

Best regards,

Thomas R.

---

<div class="post-metadata">

**Author:** ![Thomas74](https://avatars.discourse-cdn.com/v4/letter/t/3bc359/32.png) [@Thomas74](https://discuss.elastic.co/u/Thomas74)\
**Post date:** [September 11, 2020, 12:15pm UTC](https://discuss.elastic.co/t/cluster-yellow-heap-size-overload/248292/2 "2020-09-11T12:15:16Z")

</div>

I found the problem.

I mixed curator and ILM for index management.

An ILM policy has crashed because of a closed index and grown up until 673Gb.

It started to saturate memory JVM. I reopened closed index and retry ILM policy. This solved ILM problem and a new index was created.

But this was not enough. The cache had to be clean to allow reassigning. After a cleaning and a rerouting process, the cluster is now green.

Here are the command which help me to solve it 🙂 :

Get allocation explanation

```
GET /index-000170/_ilm/explain

```

Open closed index

```
POST /index-000143/_open

```

Retry ilm policy :

```
POST /index-000170/_ilm/retry 

```

Get stat of fieldata :

```
GET _stats/fielddata?fielddata_fields=*  

```

Clear cache fielddata :

```
POST /index-00016*/_cache/clear

```

Restart failed allocation

```
POST _cluster/reroute?retry_failed=true

```

Sources :

> [@"failed shard on node... ...Data too large, data for \[\<transport\_request\>\] would be" only for 3 most recent .monitoring-es indices](https://discuss.elastic.co/t/failed-shard-on-node-data-too-large-data-for-transport-request-would-be-only-for-3-most-recent-monitoring-es-indices/218827/7):
>
> Thank you @DavidTurner for the quick reply. I just discovered that command as you were responding and came back to post my findings. It turns out that many of my shards are culprits. Looking something like this: "env-stg-2020.02.20" : { "uuid" : "TgkrNGtKTwGNDeSshJ2YLQ", "primaries" : { "fielddata" : { "memory\_size\_in\_bytes" : 64716808, "evictions" : 0, "fields" : { "logmessage.keyword" : { "memory\_size\_in\_bytes" …

> **[Clear cache API | Elasticsearch Guide \[8.11\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-clearcache.html)**

I hope this can help someone a day. 🙂

---

<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:** [October 9, 2020, 12:15pm UTC](https://discuss.elastic.co/t/cluster-yellow-heap-size-overload/248292/3 "2020-10-09T12:15:30Z")

</div>

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