# Increased heap usage after updating from 7.2.0 =\> 7.8.0

**URL:** https://discuss.elastic.co/t/increased-heap-usage-after-updating-from-7-2-0-7-8-0/247510
**Category:** Elasticsearch
**Created:** [September 4, 2020, 9:51am UTC](https://discuss.elastic.co/t/increased-heap-usage-after-updating-from-7-2-0-7-8-0/247510 "2020-09-04T09:51:05Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![7ca884569f2642e2c488](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/7ca884569f2642e2c488/32/75102_2.png) [@7ca884569f2642e2c488](https://discuss.elastic.co/u/7ca884569f2642e2c488)
#### Post date: [September 4, 2020, 9:51am UTC](https://discuss.elastic.co/t/increased-heap-usage-after-updating-from-7-2-0-7-8-0/247510/1 "2020-09-04T09:51:05Z")

</div>

We updated our elastic (5 servers, two nodes each) from 7.2.0 to 7.8.0 and noticed that from this moment some new errors of type CircuitBreakingException started to occure and heap size can touch now 90-100% of available memory which was not the case on 7.2.0. Our routine didn't change.

Additional deatails and observations

1. Update was made without reindexing documents and just uses 7.2.0 data (can it affect something?)
2. We use default config for es in both cases
3. Docker container in both cases
4. Heap size is near 32Gb in both cases
5. After update we have permanent zero gc stat

```auto
"old": {
* "collection_count": 0,
* "collection_time_in_millis": 0
} 

```

which I think is strange  
6) We use bundled java in both cases  
7) I noticed that jdk changed from Oracle to AdoptOpenJdk, can it be connected with my problem?

---

<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: [September 7, 2020, 12:23am UTC](https://discuss.elastic.co/t/increased-heap-usage-after-updating-from-7-2-0-7-8-0/247510/2 "2020-09-07T00:23:38Z")

</div>

Can you post the exception you are seeing, and ideally some of the Elasticsearch logs?

---

<div class="post-metadata">

### Author: ![7ca884569f2642e2c488](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/7ca884569f2642e2c488/32/75102_2.png) [@7ca884569f2642e2c488](https://discuss.elastic.co/u/7ca884569f2642e2c488)
#### Post date: [September 8, 2020, 8:53am UTC](https://discuss.elastic.co/t/increased-heap-usage-after-updating-from-7-2-0-7-8-0/247510/3 "2020-09-08T08:53:31Z")

</div>

```auto
The remote server returned an error: (429) Too Many Requests.. Call: Status code 429 from: POST /regions/_search?typed_keys=true. ServerError: Type: circuit_breaking_exception Reason: "[parent] Data too large, data for [<http_request>] would be [32723739866/30.4gb], which is larger than the limit of [31621696716/29.4gb], real usage: [32723739456/30.4gb], new bytes reserved: [410/410b], usages [request=0/0b, fielddata=359734446/343mb, in_flight_requests=3008/2.9kb, accounting=4402798/4.1mb]"

```

---

<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 6, 2020, 8:53am UTC](https://discuss.elastic.co/t/increased-heap-usage-after-updating-from-7-2-0-7-8-0/247510/4 "2020-10-06T08:53:44Z")

</div>

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