# Problem with elastic in grafana

**URL:** <https://discuss.elastic.co/t/problem-with-elastic-in-grafana/273578>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [May 20, 2021, 6:58pm UTC](https://discuss.elastic.co/t/problem-with-elastic-in-grafana/273578 "2021-05-20T18:58:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Luis\_Garavatti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/luis_garavatti/32/84970_2.png) [@Luis\_Garavatti](https://discuss.elastic.co/u/Luis_Garavatti)\
**Post date:** [May 20, 2021, 6:58pm UTC](https://discuss.elastic.co/t/problem-with-elastic-in-grafana/273578/1 "2021-05-20T18:58:50Z")

</div>

Hi guys today I found a problem when adding my elasticsearch to graphana, besides it takes a while to load the reports, several times I get this error message and I need to delete my pod and recreate it, has anyone been there? Can you help?

Error Message:

```auto
Elasticsearch error: [parent] Data too large, data for [<http_request>] would be [2283066452/2.1gb], which is larger than the limit of [2282858086/2.1gb], real usage: [2283064856/2.1gb], new bytes reserved: [1596/1.5kb], usages [request=0/0b, fielddata=1474133989/1.3gb, in_flight_requests=1596/1.5kb, accounting=356557840/340mb]

```

Version: ElasticSearch 7.5

---

<div class="post-metadata">

**Author:** ![Julien](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/julien/32/19688_2.png) [@Julien](https://discuss.elastic.co/u/Julien)\
**Post date:** [May 20, 2021, 11:02pm UTC](https://discuss.elastic.co/t/problem-with-elastic-in-grafana/273578/2 "2021-05-20T23:02:26Z")

</div>

[Parent circuit breaker](https://www.elastic.co/guide/en/elasticsearch/reference/7.5/circuit-breaker.html#parent-circuit-breaker) is helping to prevent OOM by preventing the additional memory cost that the http\_request would have required. The main cause here is the current usage as opposed to the additional JVM Heap Usage

Mostly here you should either :

- [Increase JVM Heap Space](https://www.elastic.co/guide/en/elasticsearch/reference/7.12/advanced-configuration.html#set-jvm-heap-size) on the node
- Reduce JVM Heap usage. For example you could check field data

> [@Luis\_Garavatti](#):
>
> `fielddata=1474133989/1.3gb`

You might want to verify if usage is expected `GET /_nodes/stats/indices/fielddata?level=shards&pretty=true&fields=*` and potentially [clear fielddata cache](https://www.elastic.co/guide/en/elasticsearch/reference/7.5/indices-clearcache.html#clear-cache-api-specific-ex) in case that you find document id in there (\_id) (from 7.6 this can be [disabled](https://github.com/elastic/elasticsearch/pull/49166))

---

<div class="post-metadata">

**Author:** ![Luis\_Garavatti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/luis_garavatti/32/84970_2.png) [@Luis\_Garavatti](https://discuss.elastic.co/u/Luis_Garavatti)\
**Post date:** [May 21, 2021, 6:36pm UTC](https://discuss.elastic.co/t/problem-with-elastic-in-grafana/273578/3 "2021-05-21T18:36:35Z")

</div>

Thanks Julien, for the reply. I increase more memory to JVM, the problem its not happened still.

I have other question...

My grafana is connected to elasticsearch, but my dashboards are veryyyy slow.

My environment stay with SSD (type GP3 AWS).

I do not know what to do ☹

Exists one way to perform this?

Tks

Regards

---

<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:** [June 18, 2021, 6:37pm UTC](https://discuss.elastic.co/t/problem-with-elastic-in-grafana/273578/4 "2021-06-18T18:37:15Z")

</div>

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