# Circuit\_breaking\_exception \[parent\]
**URL:** https://discuss.elastic.co/t/circuit-breaking-exception-parent/301987
**Category:** Elasticsearch
**Created:** [April 8, 2022, 4:00pm UTC](https://discuss.elastic.co/t/circuit-breaking-exception-parent/301987 "2022-04-08T16:00:08Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@vikasp](https://discuss.elastic.co/u/vikasp)
#### Post date: [April 8, 2022, 4:00pm UTC](https://discuss.elastic.co/t/circuit-breaking-exception-parent/301987/1 "2022-04-08T16:00:08Z")
I have a Elasticsearch cluster with around more than 100 data nodes. around 30 hot nodes and the rest warm nodes.
I am coming across an issue where I just try to load data with the index pattern say logs\* in kibana discover,
Then I see a shard error saying circuit breaking exception for a shard that is on a specific node.
say data-node-a.
I resolved it just by moving that shard manually from that specific node.
This has been occuring multiple times, as I move the shard away from the same node dat-node-a,
the issue gets resolved.
Now,
To troubleshoot this or to understand why the shards on that node are giving me trouble,
what all I would need to check on that node and how do I identify the cause.
please point me to all the checks I would need to do on that. I might get to do all those tests and identify the root cause next time it occurs.
The error is:
circuit\_breaking\_exception:
data too large so and so (memory higher than it supposed to have ) [parent] breaker.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 6, 2022, 4:00pm UTC](https://discuss.elastic.co/t/circuit-breaking-exception-parent/301987/2 "2022-05-06T16:00:55Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.