# Parent circuit breaker calculation seems to be wrong with version 7.x

**URL:** https://discuss.elastic.co/t/parent-circuit-breaker-calculation-seems-to-be-wrong-with-version-7-x/183530
**Category:** Elasticsearch
**Created:** [May 30, 2019, 12:57pm UTC](https://discuss.elastic.co/t/parent-circuit-breaker-calculation-seems-to-be-wrong-with-version-7-x/183530 "2019-05-30T12:57:40Z")
**Posts on this page:** 1
**Showing post:** 23

<div class="post-metadata">

### Author: ![HenningAndersen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/henningandersen/32/48188_2.png) [@HenningAndersen](https://discuss.elastic.co/u/HenningAndersen)
#### Post date: [October 22, 2019, 7:34pm UTC](https://discuss.elastic.co/t/parent-circuit-breaker-calculation-seems-to-be-wrong-with-version-7-x/183530/23 "2019-10-22T19:34:17Z")

</div>

Hi @pjaikumar,

several other users who have run into this were using G1GC. Is that also the case for your cluster?

If so, the following change is important:

> <https://github.com/elastic/elasticsearch/pull/46169>

  
It is worthwhile double checking that the G1 settings are correct compared to that PR, i.e., that you have:

```auto
-XX:G1ReservePercent=25
-XX:InitiatingHeapOccupancyPercent=30

```

in your jvm.options file.

If you are not using G1 or you are using G1 with above settings, I would be interested in seeing your GC logs from Elasticsearch (together with exception info from log file) if this should reoccur.

---

_[View the full topic](https://discuss.elastic.co/t/parent-circuit-breaker-calculation-seems-to-be-wrong-with-version-7-x/183530)._