# OpenSearch - High Memory usage / Circuit Breaker Exceptions

**URL:** <https://forum.opensearch.org/t/opensearch-high-memory-usage-circuit-breaker-exceptions/26416>\
**Category:** OpenSearch\
**Tags:** troubleshoot\
**Created:** [August 18, 2025, 9:46am UTC](https://forum.opensearch.org/t/opensearch-high-memory-usage-circuit-breaker-exceptions/26416 "2025-08-18T09:46:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![aidevelop46](https://avatars.discourse-cdn.com/v4/letter/a/41988e/32.png) [@aidevelop46](https://forum.opensearch.org/u/aidevelop46)\
**Post date:** [August 18, 2025, 9:46am UTC](https://forum.opensearch.org/t/opensearch-high-memory-usage-circuit-breaker-exceptions/26416/1 "2025-08-18T09:46:17Z")

</div>

**Versions** (relevant - OpenSearch/Dashboard/Server OS/Browser): OpenSearch 2.11

**Describe the issue** :

In my case, my cluster started triggering numerous circuit breaker exception alerts.

**More informations about my cluster/operation:**

In this case where the circuit\_breaker occurred the document size was **3.57 KB**. I have some documents bigger than this, but i dont think the average are “too big”.

In this case where the circuit\_breaker error occurred, the document contained neither nested nor parent-child.

In my system we have several bulk requests, I also wouldn’t know how big these requests are and how many are occurring at the same time.

**Configuration** :

6 Nodes with this current configuration showed in the image below

**Relevant Logs or Screenshots** :

 ![image](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/0/03476ebc88620abb53d8f32d9c68698f44adc920.jpeg)

Despite my limited experience with Elastic, I truly believe that the reason the cluster are triggering so many circuit\_breaker requests has more to do with how I’m using Elastic than with my cluster’s configuration, which I think is “normal/good.”

I think the biggest problem is that Elastic is the single source of truth for my entire system. I don’t think Elastic is designed for that. This means I have thousands of read/write operations occurring simultaneously. Do you agree with this?

Thanks for all!

---

<div class="post-metadata">

**Author:** ![Leeroy](https://avatars.discourse-cdn.com/v4/letter/l/eb9ed0/32.png) [@Leeroy](https://forum.opensearch.org/u/Leeroy)\
**Post date:** [August 18, 2025, 5:44pm UTC](https://forum.opensearch.org/t/opensearch-high-memory-usage-circuit-breaker-exceptions/26416/2 "2025-08-18T17:44:15Z")

</div>

Hey @aidevelop46 ,

Looking at what you provided it looks that you’re using Elasticsearch? Could you confirm this? Ram usage being high might indicate that additional ram is required especially if you’re seeing issues with circuit\_breaker or high heap usage.

However it is hard to say much without first knowing more about the issue, so I first would like to ask a few questions.

- What version of Elasticsearch? Opensearch? are you using?
- Are you using roles? If so how many nodes of each are you using and what are their specs? - [Creating a cluster - OpenSearch Documentation](https://docs.opensearch.org/latest/tuning-your-cluster/)
- How many documents are you updating over say 15 minutes? Has this recently grown in number?
- Are updates being pushed in bulk? [Bulk - OpenSearch Documentation](https://docs.opensearch.org/latest/api-reference/document-apis/bulk/)

Leeroy.
