# How to fix heap size problem against big data (CircuitBreakingException)

**URL:** https://discuss.elastic.co/t/how-to-fix-heap-size-problem-against-big-data-circuitbreakingexception/245554
**Category:** Elasticsearch
**Created:** [August 19, 2020, 8:57am UTC](https://discuss.elastic.co/t/how-to-fix-heap-size-problem-against-big-data-circuitbreakingexception/245554 "2020-08-19T08:57:05Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Farid\_N](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/farid_n/32/74144_2.png) [@Farid\_N](https://discuss.elastic.co/u/Farid_N)
#### Post date: [August 19, 2020, 8:57am UTC](https://discuss.elastic.co/t/how-to-fix-heap-size-problem-against-big-data-circuitbreakingexception/245554/1 "2020-08-19T08:57:05Z")

</div>

Hi  
I have an issue with my cluster.  
I want to know how can I fix the heap memory against big data?  
Consider that I can`t increase the size or another memory... What is the solution?

---

<div class="post-metadata">

### Author: ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [August 19, 2020, 10:29am UTC](https://discuss.elastic.co/t/how-to-fix-heap-size-problem-against-big-data-circuitbreakingexception/245554/2 "2020-08-19T10:29:19Z")

</div>

What exactly is causing the heap usage? How much data do you have in the cluster? How many indices and shards? How much are you indexing per day? Are you running very memory intensive queries? Which version are you using?

---

<div class="post-metadata">

### Author: ![Farid\_N](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/farid_n/32/74144_2.png) [@Farid\_N](https://discuss.elastic.co/u/Farid_N)
#### Post date: [August 19, 2020, 10:51am UTC](https://discuss.elastic.co/t/how-to-fix-heap-size-problem-against-big-data-circuitbreakingexception/245554/3 "2020-08-19T10:51:20Z")

</div>

Thank`s for your response... Imagine I have 3 indices and 3 shards All 3 indices reach 1 TB traffic per day and always I`ll get throttle on my elasticsearch because of the size of data. Heap memory goes down...  
Is there any solution for heap memory? I don`t want to loos my entire logs and also unfortunately, I can`t increase the size of heap memory, or use another memory for that

I used elasticsearch 7.8.1

---

<div class="post-metadata">

### Author: ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [August 19, 2020, 10:55am UTC](https://discuss.elastic.co/t/how-to-fix-heap-size-problem-against-big-data-circuitbreakingexception/245554/4 "2020-08-19T10:55:45Z")

</div>

What does you workload look like? What is the full output of the cluster stats API?

---

<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: [September 16, 2020, 10:55am UTC](https://discuss.elastic.co/t/how-to-fix-heap-size-problem-against-big-data-circuitbreakingexception/245554/5 "2020-09-16T10:55:56Z")

</div>

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