# New used memory \[6.4gb\] for data of \[\<reused\_arrays\>\] would be larger than configured breaker

**URL:** https://discuss.elastic.co/t/new-used-memory-6-4gb-for-data-of-reused-arrays-would-be-larger-than-configured-breaker/51643
**Category:** Elasticsearch
**Created:** [June 2, 2016, 4:59am UTC](https://discuss.elastic.co/t/new-used-memory-6-4gb-for-data-of-reused-arrays-would-be-larger-than-configured-breaker/51643 "2016-06-02T04:59:40Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![vin01](https://avatars.discourse-cdn.com/v4/letter/v/bc8723/32.png) [@vin01](https://discuss.elastic.co/u/vin01)
#### Post date: [June 2, 2016, 4:59am UTC](https://discuss.elastic.co/t/new-used-memory-6-4gb-for-data-of-reused-arrays-would-be-larger-than-configured-breaker/51643/1 "2016-06-02T04:59:40Z")

</div>

Elasticsearch version 2.3.1.

For searches which include heavy aggregation over long period of time (1 year data in this case), i start getting :-

> WARN request:143 - [request] New used memory 6915236168 [6.4gb] for data of [reused\_arrays] would be larger than configured breaker: 6871947673 [6.3gb], breaking

I believe this is the limit imposed by :-

```
indices.breaker.request.limit

```

And it doesn't seem to be dynamically updateable. I got an OOM Error because of it, despite the breaker limit set.  
Is there a way to clear the memory dynamically? I clear the cache using \_cache/clear if \_cat/fielddata goes 5+ GB using a curl request running periodically, is there something similar I can do to prevent this one as well?

---

<div class="post-metadata">

### Author: ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)
#### Post date: [June 3, 2016, 3:35pm UTC](https://discuss.elastic.co/t/new-used-memory-6-4gb-for-data-of-reused-arrays-would-be-larger-than-configured-breaker/51643/2 "2016-06-03T15:35:21Z")

</div>

Can you share an example of the "heavy aggregation"? There might be things which can be done to reduce the cost of the request e.g. using breadth\_first settings.

[https://www.elastic.co/guide/en/elasticsearch/guide/2.x/\_preventing\_combinatorial\_explosions.html](https://www.elastic.co/guide/en/elasticsearch/guide/2.x/_preventing_combinatorial_explosions.html)

---

<div class="post-metadata">

### Author: ![vin01](https://avatars.discourse-cdn.com/v4/letter/v/bc8723/32.png) [@vin01](https://discuss.elastic.co/u/vin01)
#### Post date: [June 3, 2016, 3:41pm UTC](https://discuss.elastic.co/t/new-used-memory-6-4gb-for-data-of-reused-arrays-would-be-larger-than-configured-breaker/51643/3 "2016-06-03T15:41:00Z")

</div>

Yeah, I am working on improving those for better alternatives.

My concern was that despite the breaker limit set, an OOM happens .. that's the exact purpose of having the breaker..

---

<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: [July 5, 2017, 10:46pm UTC](https://discuss.elastic.co/t/new-used-memory-6-4gb-for-data-of-reused-arrays-would-be-larger-than-configured-breaker/51643/4 "2017-07-05T22:46:22Z")

</div>