# CircuitBreakingException: \[parent\] Data too large

**URL:** <https://discuss.elastic.co/t/circuitbreakingexception-parent-data-too-large/253299>\
**Category:** Elasticsearch\
**Created:** [October 26, 2020, 11:28am UTC](https://discuss.elastic.co/t/circuitbreakingexception-parent-data-too-large/253299 "2020-10-26T11:28:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Grant\_Zietsman](https://avatars.discourse-cdn.com/v4/letter/g/a9a28c/32.png) [@Grant\_Zietsman](https://discuss.elastic.co/u/Grant_Zietsman)\
**Post date:** [October 26, 2020, 11:28am UTC](https://discuss.elastic.co/t/circuitbreakingexception-parent-data-too-large/253299/1 "2020-10-26T11:28:49Z")

</div>

Running into a CircuitBreakingException when doing a restore for Elasticsearch 7.7.1

Based on this [issue](https://discuss.elastic.co/t/circuitbreakingexception-parent-data-too-large-in-es-7-x/192801), I suspect that I can try disabling `indices.breaker.total.use_real_memory`. Alternatively, I can try reducing `CMSInitiatingOccupancyFraction`. Are there any other recommendations? I don't have much experience with JVM tuning.

**JVM version (`java -version`):**

```auto
openjdk version "1.8.0_265"
OpenJDK Runtime Environment (build 1.8.0_265-8u265-b01-0ubuntu2~16.04-b01)
OpenJDK 64-Bit Server VM (build 25.265-b01, mixed mode)

```

**ES Log:**

```auto
Failed to complete action: restore. <class 'curator.exceptions.FailedExecution'>: Exception encountered. Rerun with loglevel DEBUG and/or check Elasticsearch logs for more information. Exception: Unable to obtain recovery information for specified indices. Error: TransportError(429, 'circuit_breaking_exception', '[parent] Data too large, data for [<http_request>] would be [12543328208/11.6gb], which is larger than the limit of [12240656793/11.3gb], real usage: [12543328208/11.6gb], new bytes reserved: [0/0b], usages [request=0/0b, fielddata=0/0b, in_flight_requests=0/0b, accounting=1592100/1.5mb]')

```

**jvm.option:**

```auto
-Xms12g
-Xmx12g
-XX:+UseConcMarkSweepGC
-XX:CMSInitiatingOccupancyFraction=75
-XX:+UseCMSInitiatingOccupancyOnly
-XX:+AlwaysPreTouch
-Xss1m
-XX:-OmitStackTraceInFastThrow
8:-XX:+PrintGCDetails
8:-XX:+PrintGCDateStamps
8:-XX:+PrintTenuringDistribution
8:-XX:+PrintGCApplicationStoppedTime
8:-Xloggc:/var/log/elasticsearch/gc.log
8:-XX:+UseGCLogFileRotation
8:-XX:NumberOfGCLogFiles=32
8:-XX:GCLogFileSize=64m

```

---

<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:** [November 23, 2020, 11:28am UTC](https://discuss.elastic.co/t/circuitbreakingexception-parent-data-too-large/253299/2 "2020-11-23T11:28:54Z")

</div>

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