# CircuitBreakingException: \[parent\] Data too large IN ES 7.x **URL:** \ **Category:** Elasticsearch\ **Created:** [July 30, 2019, 1:44am UTC](https://discuss.elastic.co/t/circuitbreakingexception-parent-data-too-large-in-es-7-x/192801 "2019-07-30T01:44:22Z")\ **Posts on this page:** 1\ **Showing post:** 14
**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:** [September 4, 2019, 6:47am UTC](https://discuss.elastic.co/t/circuitbreakingexception-parent-data-too-large-in-es-7-x/192801/14 "2019-09-04T06:47:49Z")
Hi @LoadingZhang, thanks for reporting back on this. Unfortunately, I made a mistake in my original post in that `InitiatingHeapOccupancyPercent` should really have been set to 30. I have edited my post above to avoid confusion if others read this post. The JVM should auto-tune this parameter after a while, it only uses the original IHOP value until it has a better estimate of what it should be itself. So your test is certainly still valuable, confirming that the `G1ReservePercent` does reserve enough heap to avoid circuit breaking in your case. I have not looked too much into ZGC yet, since it still has experimental status. You will need something like the `SoftMaxHeapSize` option to make it compatible with real memory circuit breaker. Also, you should notice that ZGC does not support compressed oops, meaning you will likely need more heap since all references need 64 bits rather than 32 bits. This will also in itself lead to some performance degradation (reduced cpu cache efficiency and more data to fetch from RAM). --- _[View the full topic](https://discuss.elastic.co/t/circuitbreakingexception-parent-data-too-large-in-es-7-x/192801)._