# Elastic search(elasticsearch-8.9.2) stopping abruptly

**URL:** <https://discuss.elastic.co/t/elastic-search-elasticsearch-8-9-2-stopping-abruptly/382548>\
**Category:** Elastic Search\
**Created:** [October 9, 2025, 12:29pm UTC](https://discuss.elastic.co/t/elastic-search-elasticsearch-8-9-2-stopping-abruptly/382548 "2025-10-09T12:29:30Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [October 9, 2025, 12:42pm UTC](https://discuss.elastic.co/t/elastic-search-elasticsearch-8-9-2-stopping-abruptly/382548/2 "2025-10-09T12:42:05Z")

</div>

Hi @Nataraj,

Welcome! That GC error suggests that you're hitting a circuit breaker. What is the health and JVM usage of your cluster?

```auto
GET _cluster/health
GET _cat/nodes?v=true&h=name,node*,heap*
GET _nodes/stats/breaker

```

What type of query/ operation are you running when this is triggered? It might be down to the query size.

The below resources may also help you investigate and remediate the problem:

> [@ElasticSearch cluster down due to high memory usage](https://discuss.elastic.co/t/elasticsearch-cluster-down-due-to-high-memory-usage/337975):
>
> I have ran some queries on ES, which fetched huge amount of data and due to that Memory utilization reached high and ES cluster went down. Below is the error that ES-java client has thrown {"error":{"root\_cause":[{"type":"circuit\_breaking\_exception","reason":"[parent] Data too large, data for [\<http\_request\>] would be [4031859746/3.7gb], which is larger than the limit of [3865051136/3.5gb], real usage: [4031859168/3.7gb], new bytes reserved: [578/578b], usages [model\_inference=0/0b, inflight\_r…

> **[GC did not bring memory usage down before after allocations duration - Common...](https://opster.com/analysis/elasticsearch-gc-did-not-bring-memory-usage-down-before-after-allocations-duration/)**
>
> A detailed guide on how to resolve errors related to "GC did not bring memory usage down before after allocations duration" - common causes and fixes

> **[Circuit breaker errors | Elastic Docs](https://www.elastic.co/docs/troubleshoot/elasticsearch/circuit-breaker-errors)**
>
> Elasticsearch uses circuit breakers to prevent nodes from running out of JVM heap memory. If Elasticsearch estimates an operation would exceed a circuit...

Hope that helps!

---

_[View the full topic](https://discuss.elastic.co/t/elastic-search-elasticsearch-8-9-2-stopping-abruptly/382548)._
