# CircuitBreakingException: \[parent\] Data too large IN ES 7.x

**URL:** <https://discuss.elastic.co/t/circuitbreakingexception-parent-data-too-large-in-es-7-x/192801>\
**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:** 19

<div class="post-metadata">

**Author:** ![Yakir\_Gibraltar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yakir_gibraltar/32/54319_2.png) [@Yakir\_Gibraltar](https://discuss.elastic.co/u/Yakir_Gibraltar)\
**Post date:** [October 10, 2019, 11:26am UTC](https://discuss.elastic.co/t/circuitbreakingexception-parent-data-too-large-in-es-7-x/192801/19 "2019-10-10T11:26:49Z")

</div>

Just to update, we solved the issue of Azul Zing JDK with `-XX:GPGCTargetPeakHeapOccupancyPercent=95`  
Our jvm.conf right now:

```auto
-Dio.netty.noKeySetOptimization=true
-Dio.netty.noUnsafe=true
-Dio.netty.recycler.maxCapacityPerThread=0
-Djava.awt.headless=true
-Djna.nosys=true
-Dlog4j.shutdownHookEnabled=false
-Dlog4j2.disable.jmx=true
-XX:+AlwaysPreTouch
-XX:+HeapDumpOnOutOfMemoryError
-XX:-OmitStackTraceInFastThrow
-XX:GPGCTargetPeakHeapOccupancyPercent=95
-Xloggc:/var/log/elasticsearch/dba/gc.log
-Xms32g
-Xmx32g
-Xss1m
-server
-verbose:gc

```

---

_[View the full topic](https://discuss.elastic.co/t/circuitbreakingexception-parent-data-too-large-in-es-7-x/192801)._