# In ES 7.8 parent breaker is tripping a lot and causing unallocation of shards **URL:** \ **Category:** Elasticsearch\ **Created:** [July 14, 2022, 11:14am UTC](https://discuss.elastic.co/t/in-es-7-8-parent-breaker-is-tripping-a-lot-and-causing-unallocation-of-shards/309635 "2022-07-14T11:14:00Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![sreekanth](https://avatars.discourse-cdn.com/v4/letter/s/e47774/32.png) [@sreekanth](https://discuss.elastic.co/u/sreekanth)\ **Post date:** [July 14, 2022, 11:14am UTC](https://discuss.elastic.co/t/in-es-7-8-parent-breaker-is-tripping-a-lot-and-causing-unallocation-of-shards/309635/1 "2022-07-14T11:14:00Z")
We have an 8 node cluster and our load (mainly bulk ingest) is pretty high. Earlier the same load was handled well by 6 nodes in ES6.8. Now after moving to 7.8, we see many replica shards get unallocated during load. **allocation api tells the reason as** ```auto "details" : "failed shard on node [zC2EkvPLQiWpJ_YjnllD5w]: failed to perform indices:data/write/bulk[s] on replica [10fc5a76ee7042b3ad5bf620ac9fdb39-psrtenant15-fa-cse-asset][0], node[zC2EkvPLQiWpJ_YjnllD5w], [R], s[STARTED], a[id=6xKPtXO5TeyjZL12zRA7rA], failure RemoteTransportException[[psrnativefa112521-esdata4][100.104.145.203:9300][indices:data/write/bulk[s][r]]]; nested: CircuitBreakingException[[parent] Data too large, data for [indices:data/write/bulk[s][r]] would be [31182253448/29gb], which is larger than the limit of [30601641984/28.5gb], real usage: [31181936024/29gb], new bytes reserved: [317424/309.9kb], usages [request=256/256b, fielddata=64205239/61.2mb, in_flight_requests=60178048/57.3mb, accounting=1148757896/1gb]]; ",` ``` **Issue** : Basically parent breaker is hitting the limit of 28.5GB and our heap is 30GB. If We increase the parent breaker to 29.5GB, I see fewer shards getting un allocated but still the issue resides. Our JVM args already have below args which should help in this case as per a few old discussions. But not helping much. ```auto -XX:G1ReservePercent=25 -XX:InitiatingHeapOccupancyPercent=30 ``` Please let us know what can be done to avoid this. We can disable this breaker but there will be a purpose for this and don't want to disable it. ---
**Author:** ![sreekanth](https://avatars.discourse-cdn.com/v4/letter/s/e47774/32.png) [@sreekanth](https://discuss.elastic.co/u/sreekanth)\ **Post date:** [July 18, 2022, 5:10am UTC](https://discuss.elastic.co/t/in-es-7-8-parent-breaker-is-tripping-a-lot-and-causing-unallocation-of-shards/309635/3 "2022-07-18T05:10:28Z")
Hi Team, any update on this? Few queries - How frequently this parent breaker usage is calculated? - While calculating parent breaker usage, do you just pick the latest current heap usage? Or after GC usage? As in my case, JVM usage is going to \> 29GB several times but GC is bringing it down to \<22GB. So this should not be considered as circuit break right? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [July 18, 2022, 10:58am UTC](https://discuss.elastic.co/t/in-es-7-8-parent-breaker-is-tripping-a-lot-and-causing-unallocation-of-shards/309635/4 "2022-07-18T10:58:08Z")
> [@sreekanth](#): > > Now after moving to 7.8 7.8 is really old, long past [EOL](https://www.elastic.co/support/eol), and newer versions are much more memory-efficient. > [@sreekanth](#): > > Please let us know what can be done to avoid this. The first thing to try is to upgrade to a version that hasn't passed EOL. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 15, 2022, 10:58am UTC](https://discuss.elastic.co/t/in-es-7-8-parent-breaker-is-tripping-a-lot-and-causing-unallocation-of-shards/309635/5 "2022-08-15T10:58:35Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.