From 4fab97240e8f4b14f064d3795cb96ee9ebef6b09 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tanja=20Mili=C4=8Di=C4=87?= <156105538+tanja-milicic@users.noreply.github.com> Date: Mon, 5 Jan 2026 12:47:18 +0100 Subject: [PATCH 01/11] Update circuit-breaker-errors.md --- .../elasticsearch/circuit-breaker-errors.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/troubleshoot/elasticsearch/circuit-breaker-errors.md b/troubleshoot/elasticsearch/circuit-breaker-errors.md index c868d5461c..49c2a0e25a 100644 --- a/troubleshoot/elasticsearch/circuit-breaker-errors.md +++ b/troubleshoot/elasticsearch/circuit-breaker-errors.md @@ -24,7 +24,7 @@ See [this video](https://www.youtube.com/watch?v=k3wYlRVbMSw) for a walkthrough **Error messages** -If a request triggers a circuit breaker, {{es}} returns an error with a `429` HTTP status code. +A circuit breaker trips when it prevents a request from executing in order to protect the node's stability. When a request triggers a circuit breaker, {{es}} returns an error with a `429` HTTP status code. ```js { @@ -45,6 +45,20 @@ If a request triggers a circuit breaker, {{es}} returns an error with a `429` HT Caused by: org.elasticsearch.common.breaker.CircuitBreakingException: [parent] Data too large, data for [] would be [num/numGB], which is larger than the limit of [num/numGB], usages [request=0/0b, fielddata=num/numKB, in_flight_requests=num/numGB, accounting=num/numGB] ``` +**Check circuit breaker statistics** + +You can use the [node stats API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-nodes-stats) to get statistics about the circuit breaker per node. + +```console +GET _nodes/stats?filter_path=nodes.*.breakers +``` + +This will show you: +- Estimated memory used, in bytes, for the operation. +- Memmory limit for the circuit breaker. +- Total number of times the circuit breaker has been triggered and prevented an out of memory error. +- And an overhead which is a constant that all estimates for the circuit breaker are multiplied with to calculate a final estimate. + **Check JVM memory usage** If you’ve enabled Stack Monitoring, you can view JVM memory usage in {{kib}}. In the main menu, click **Stack Monitoring**. On the Stack Monitoring **Overview** page, click **Nodes**. The **JVM Heap** column lists the current memory usage for each node. From 716ad43bf770e069358d34e1a7d492168a7a85d5 Mon Sep 17 00:00:00 2001 From: Tanja Milicic Date: Tue, 6 Jan 2026 11:57:12 +0100 Subject: [PATCH 02/11] Add description of circuit breaker types and memory evaluation --- .../elasticsearch/circuit-breaker-errors.md | 27 ++++++++++++++++--- 1 file changed, 23 insertions(+), 4 deletions(-) diff --git a/troubleshoot/elasticsearch/circuit-breaker-errors.md b/troubleshoot/elasticsearch/circuit-breaker-errors.md index 49c2a0e25a..da215739b2 100644 --- a/troubleshoot/elasticsearch/circuit-breaker-errors.md +++ b/troubleshoot/elasticsearch/circuit-breaker-errors.md @@ -18,8 +18,6 @@ See [this video](https://www.youtube.com/watch?v=k3wYlRVbMSw) for a walkthrough :::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md ::: - - ## Diagnose circuit breaker errors [diagnose-circuit-breaker-errors] **Error messages** @@ -54,7 +52,7 @@ GET _nodes/stats?filter_path=nodes.*.breakers ``` This will show you: -- Estimated memory used, in bytes, for the operation. +- Estimated memory used for the operation. - Memmory limit for the circuit breaker. - Total number of times the circuit breaker has been triggered and prevented an out of memory error. - And an overhead which is a constant that all estimates for the circuit breaker are multiplied with to calculate a final estimate. @@ -75,7 +73,6 @@ To get the JVM memory usage for each circuit breaker, use the [node stats API](h GET _nodes/stats/breaker ``` - ## Prevent circuit breaker errors [prevent-circuit-breaker-errors] **Reduce JVM memory pressure** @@ -93,3 +90,25 @@ If you’ve triggered the fielddata circuit breaker and can’t disable fielddat ```console POST _cache/clear?fielddata=true ``` + +## Circuit Breaker Types + +[Circuit breaker types](elasticsearch://reference/elasticsearch/configuration-reference/circuit-breaker-settings.md) are manually defined for known expensive code paths with a sum-up [parent circuit breaker](elasticsearch://reference/elasticsearch/configuration-reference/circuit-breaker-settings.md#parent-circuit-breaker). Breakers need to be resolved per breaker type; common examples: + +- `accounting`: Lucene segments and their overhead. Commonly indicates need to [force merge](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-forcemerge) or [fix large shards](elasticsearch://deploy-manage/production-guidance/optimize-performance/size-shards.md). +- `fielddata`: [field data] and [global ordinals] +- `eql_sequence`: [eql sequences] +- `request`: API request bodies. Commonly for [Bulk] sizes too large +- `inflight_requests`: total API network bytes +- `script`: [scripts] +- `regex`: [regex] + +**Memory evaluation** + +Circuit breakers may either directly evaluate memory usage estimates or indirectly limit operations that are likely to cause excessive memory consumption. For example, the `script` circuit breaker checks memory indirectly by rate-limiting Painless/Mustache script compilations. However, even with circuit breakers in place, nodes can still encounter out-of-memory (OOM) conditions. This can occur, for example, because: + +- Circuit breaker relies on point-in-time memory usage estimations. +- Parallel operations may still heap DOS-attack the node even with `parent` circuit breakers. +- Certain dynamic operations can quickly consume substantial memory. For example [aggregations](elasticsearch://explore-analyze/query-filter/aggregations.md) and [complex queries](elasticsearch://reference/query-languages/query-dsl/compound-queries). +Circuit breakers protect JVM heap memory, but if OOM occurs due to non-heap memory; for example JVM for complication (code cache) or thread stacks. + From ecfc4dbb04a452cc736a4ac743c1c526b38335f9 Mon Sep 17 00:00:00 2001 From: Tanja Milicic Date: Tue, 6 Jan 2026 11:58:45 +0100 Subject: [PATCH 03/11] Fix new lines --- troubleshoot/elasticsearch/circuit-breaker-errors.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/troubleshoot/elasticsearch/circuit-breaker-errors.md b/troubleshoot/elasticsearch/circuit-breaker-errors.md index da215739b2..2b6f5ad7a6 100644 --- a/troubleshoot/elasticsearch/circuit-breaker-errors.md +++ b/troubleshoot/elasticsearch/circuit-breaker-errors.md @@ -7,6 +7,8 @@ products: - id: elasticsearch --- + + # Circuit breaker errors [circuit-breaker-errors] {{es}} uses [circuit breakers](elasticsearch://reference/elasticsearch/configuration-reference/circuit-breaker-settings.md) to prevent nodes from running out of JVM heap memory. If Elasticsearch estimates an operation would exceed a circuit breaker, it stops the operation and returns an error. @@ -73,6 +75,7 @@ To get the JVM memory usage for each circuit breaker, use the [node stats API](h GET _nodes/stats/breaker ``` + ## Prevent circuit breaker errors [prevent-circuit-breaker-errors] **Reduce JVM memory pressure** From df1771f8598c6ec510379add9bf8050be52fa52e Mon Sep 17 00:00:00 2001 From: Tanja Milicic Date: Tue, 6 Jan 2026 12:00:27 +0100 Subject: [PATCH 04/11] Fix new lines --- troubleshoot/elasticsearch/circuit-breaker-errors.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/troubleshoot/elasticsearch/circuit-breaker-errors.md b/troubleshoot/elasticsearch/circuit-breaker-errors.md index 2b6f5ad7a6..67b9fa72ae 100644 --- a/troubleshoot/elasticsearch/circuit-breaker-errors.md +++ b/troubleshoot/elasticsearch/circuit-breaker-errors.md @@ -7,8 +7,6 @@ products: - id: elasticsearch --- - - # Circuit breaker errors [circuit-breaker-errors] {{es}} uses [circuit breakers](elasticsearch://reference/elasticsearch/configuration-reference/circuit-breaker-settings.md) to prevent nodes from running out of JVM heap memory. If Elasticsearch estimates an operation would exceed a circuit breaker, it stops the operation and returns an error. @@ -20,6 +18,8 @@ See [this video](https://www.youtube.com/watch?v=k3wYlRVbMSw) for a walkthrough :::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md ::: + + ## Diagnose circuit breaker errors [diagnose-circuit-breaker-errors] **Error messages** From b107d25463b8bdaef9de84e41f9314ef7393b540 Mon Sep 17 00:00:00 2001 From: Stef Nestor <26751266+stefnestor@users.noreply.github.com> Date: Tue, 6 Jan 2026 09:20:25 -0700 Subject: [PATCH 05/11] =?UTF-8?q?grammar+links=20=F0=9F=99=8F?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Vlada Chirmicci --- .../elasticsearch/circuit-breaker-errors.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/troubleshoot/elasticsearch/circuit-breaker-errors.md b/troubleshoot/elasticsearch/circuit-breaker-errors.md index 67b9fa72ae..e2750e6cc7 100644 --- a/troubleshoot/elasticsearch/circuit-breaker-errors.md +++ b/troubleshoot/elasticsearch/circuit-breaker-errors.md @@ -24,7 +24,7 @@ See [this video](https://www.youtube.com/watch?v=k3wYlRVbMSw) for a walkthrough **Error messages** -A circuit breaker trips when it prevents a request from executing in order to protect the node's stability. When a request triggers a circuit breaker, {{es}} returns an error with a `429` HTTP status code. +A circuit breaker trips to prevent a request from executing in order to protect the node's stability. When a request triggers a circuit breaker, {{es}} [rejects the request](/troubleshoot/elasticsearch/rejected-requests.md) with a `429` HTTP status code error. ```js { @@ -53,10 +53,10 @@ You can use the [node stats API](https://www.elastic.co/docs/api/doc/elasticsear GET _nodes/stats?filter_path=nodes.*.breakers ``` -This will show you: +The response provides the following information: - Estimated memory used for the operation. - Memmory limit for the circuit breaker. -- Total number of times the circuit breaker has been triggered and prevented an out of memory error. +- Total number of times the circuit breaker has been triggered and prevented an out of memory error since node uptime. - And an overhead which is a constant that all estimates for the circuit breaker are multiplied with to calculate a final estimate. **Check JVM memory usage** @@ -94,11 +94,11 @@ If you’ve triggered the fielddata circuit breaker and can’t disable fielddat POST _cache/clear?fielddata=true ``` -## Circuit Breaker Types +## Circuit breaker types [Circuit breaker types](elasticsearch://reference/elasticsearch/configuration-reference/circuit-breaker-settings.md) are manually defined for known expensive code paths with a sum-up [parent circuit breaker](elasticsearch://reference/elasticsearch/configuration-reference/circuit-breaker-settings.md#parent-circuit-breaker). Breakers need to be resolved per breaker type; common examples: -- `accounting`: Lucene segments and their overhead. Commonly indicates need to [force merge](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-forcemerge) or [fix large shards](elasticsearch://deploy-manage/production-guidance/optimize-performance/size-shards.md). +- `accounting`: Lucene segments and their overhead. Commonly indicates need to [force merge](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-forcemerge) or [fix large shards](/deploy-manage/production-guidance/optimize-performance/size-shards.md). - `fielddata`: [field data] and [global ordinals] - `eql_sequence`: [eql sequences] - `request`: API request bodies. Commonly for [Bulk] sizes too large @@ -112,6 +112,6 @@ Circuit breakers may either directly evaluate memory usage estimates or indirect - Circuit breaker relies on point-in-time memory usage estimations. - Parallel operations may still heap DOS-attack the node even with `parent` circuit breakers. -- Certain dynamic operations can quickly consume substantial memory. For example [aggregations](elasticsearch://explore-analyze/query-filter/aggregations.md) and [complex queries](elasticsearch://reference/query-languages/query-dsl/compound-queries). -Circuit breakers protect JVM heap memory, but if OOM occurs due to non-heap memory; for example JVM for complication (code cache) or thread stacks. +- Certain dynamic operations can quickly consume substantial memory. For example [aggregations](/explore-analyze/query-filter/aggregations.md) and [complex queries](elasticsearch://reference/query-languages/query-dsl/compound-queries.md). +Circuit breakers protect the node's JVM heap. OOM can still trigger due to non-heap memory, for example within the compilation or thread stacks. From 8d60b20ed43387461b84ec62cd68c462e3c252e1 Mon Sep 17 00:00:00 2001 From: Tanja Milicic Date: Wed, 7 Jan 2026 10:27:42 +0100 Subject: [PATCH 06/11] remove circuit breaker types --- troubleshoot/elasticsearch/circuit-breaker-errors.md | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/troubleshoot/elasticsearch/circuit-breaker-errors.md b/troubleshoot/elasticsearch/circuit-breaker-errors.md index e2750e6cc7..6923f2c6d9 100644 --- a/troubleshoot/elasticsearch/circuit-breaker-errors.md +++ b/troubleshoot/elasticsearch/circuit-breaker-errors.md @@ -94,18 +94,6 @@ If you’ve triggered the fielddata circuit breaker and can’t disable fielddat POST _cache/clear?fielddata=true ``` -## Circuit breaker types - -[Circuit breaker types](elasticsearch://reference/elasticsearch/configuration-reference/circuit-breaker-settings.md) are manually defined for known expensive code paths with a sum-up [parent circuit breaker](elasticsearch://reference/elasticsearch/configuration-reference/circuit-breaker-settings.md#parent-circuit-breaker). Breakers need to be resolved per breaker type; common examples: - -- `accounting`: Lucene segments and their overhead. Commonly indicates need to [force merge](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-forcemerge) or [fix large shards](/deploy-manage/production-guidance/optimize-performance/size-shards.md). -- `fielddata`: [field data] and [global ordinals] -- `eql_sequence`: [eql sequences] -- `request`: API request bodies. Commonly for [Bulk] sizes too large -- `inflight_requests`: total API network bytes -- `script`: [scripts] -- `regex`: [regex] - **Memory evaluation** Circuit breakers may either directly evaluate memory usage estimates or indirectly limit operations that are likely to cause excessive memory consumption. For example, the `script` circuit breaker checks memory indirectly by rate-limiting Painless/Mustache script compilations. However, even with circuit breakers in place, nodes can still encounter out-of-memory (OOM) conditions. This can occur, for example, because: From 66587bf6bbcfbfc712274e245958d51a8b3c77b6 Mon Sep 17 00:00:00 2001 From: Tanja Milicic Date: Wed, 7 Jan 2026 12:21:59 +0100 Subject: [PATCH 07/11] Add the _cat/citcuit-breaker example --- troubleshoot/elasticsearch/circuit-breaker-errors.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/troubleshoot/elasticsearch/circuit-breaker-errors.md b/troubleshoot/elasticsearch/circuit-breaker-errors.md index 6923f2c6d9..ce902d905f 100644 --- a/troubleshoot/elasticsearch/circuit-breaker-errors.md +++ b/troubleshoot/elasticsearch/circuit-breaker-errors.md @@ -53,6 +53,11 @@ You can use the [node stats API](https://www.elastic.co/docs/api/doc/elasticsear GET _nodes/stats?filter_path=nodes.*.breakers ``` +**Since version 9.3.0**, you can use [`_cat/circuit_breaker`](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-circuit-breaker) API +```console +GET /_cat/circuit_breaker +``` + The response provides the following information: - Estimated memory used for the operation. - Memmory limit for the circuit breaker. @@ -94,7 +99,7 @@ If you’ve triggered the fielddata circuit breaker and can’t disable fielddat POST _cache/clear?fielddata=true ``` -**Memory evaluation** +## Memory evaluation Circuit breakers may either directly evaluate memory usage estimates or indirectly limit operations that are likely to cause excessive memory consumption. For example, the `script` circuit breaker checks memory indirectly by rate-limiting Painless/Mustache script compilations. However, even with circuit breakers in place, nodes can still encounter out-of-memory (OOM) conditions. This can occur, for example, because: From 8809a79ae2a915eb8e9d2b76259a18afd65e7cb0 Mon Sep 17 00:00:00 2001 From: Tanja Milicic Date: Wed, 7 Jan 2026 12:29:48 +0100 Subject: [PATCH 08/11] remove _cat/circuit-breaker example --- troubleshoot/elasticsearch/circuit-breaker-errors.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/troubleshoot/elasticsearch/circuit-breaker-errors.md b/troubleshoot/elasticsearch/circuit-breaker-errors.md index ce902d905f..9efd821151 100644 --- a/troubleshoot/elasticsearch/circuit-breaker-errors.md +++ b/troubleshoot/elasticsearch/circuit-breaker-errors.md @@ -53,11 +53,6 @@ You can use the [node stats API](https://www.elastic.co/docs/api/doc/elasticsear GET _nodes/stats?filter_path=nodes.*.breakers ``` -**Since version 9.3.0**, you can use [`_cat/circuit_breaker`](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-circuit-breaker) API -```console -GET /_cat/circuit_breaker -``` - The response provides the following information: - Estimated memory used for the operation. - Memmory limit for the circuit breaker. From af30eb166d2bc20f2b98241c7fd2808644e20381 Mon Sep 17 00:00:00 2001 From: Tanja Milicic Date: Wed, 7 Jan 2026 16:19:32 +0100 Subject: [PATCH 09/11] add _cat/circuit-brealer api example --- troubleshoot/elasticsearch/circuit-breaker-errors.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/troubleshoot/elasticsearch/circuit-breaker-errors.md b/troubleshoot/elasticsearch/circuit-breaker-errors.md index 9efd821151..54b8d09365 100644 --- a/troubleshoot/elasticsearch/circuit-breaker-errors.md +++ b/troubleshoot/elasticsearch/circuit-breaker-errors.md @@ -47,12 +47,19 @@ Caused by: org.elasticsearch.common.breaker.CircuitBreakingException: [parent] D **Check circuit breaker statistics** -You can use the [node stats API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-nodes-stats) to get statistics about the circuit breaker per node. +To get statistics about the circuit breaker per node. You can use: + +The [node stats API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-nodes-stats): ```console GET _nodes/stats?filter_path=nodes.*.breakers ``` +{applies_to}`stack: ga 9.3` Or [/_cat/circuit_breaker](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-circuit-breaker) API: +```console +GET /_cat/circuit_breaker/ +``` + The response provides the following information: - Estimated memory used for the operation. - Memmory limit for the circuit breaker. From f117e6e0c9509d28d2558b0b6e19f45953bd7907 Mon Sep 17 00:00:00 2001 From: Vlada Chirmicci Date: Wed, 7 Jan 2026 16:12:10 +0000 Subject: [PATCH 10/11] Adding an applies-switch to make use of the new circuit breakers API --- .../elasticsearch/circuit-breaker-errors.md | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/troubleshoot/elasticsearch/circuit-breaker-errors.md b/troubleshoot/elasticsearch/circuit-breaker-errors.md index 54b8d09365..971db90a50 100644 --- a/troubleshoot/elasticsearch/circuit-breaker-errors.md +++ b/troubleshoot/elasticsearch/circuit-breaker-errors.md @@ -47,18 +47,26 @@ Caused by: org.elasticsearch.common.breaker.CircuitBreakingException: [parent] D **Check circuit breaker statistics** -To get statistics about the circuit breaker per node. You can use: +To get statistics about the circuit breaker per node. Use one of the following: -The [node stats API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-nodes-stats): +::::{applies-switch} + +:::{applies-item} { "stack": "ga" } +Use the [get node statistics](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-nodes-stats) API: ```console GET _nodes/stats?filter_path=nodes.*.breakers ``` +::: -{applies_to}`stack: ga 9.3` Or [/_cat/circuit_breaker](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-circuit-breaker) API: +:::{applies-item} { "stack": "ga 9.3" } +Use the [get circuit breakers statistics](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-circuit-breaker) API: ```console GET /_cat/circuit_breaker/ ``` +::: + +:::: The response provides the following information: - Estimated memory used for the operation. From 1887f6ea45bf52283d95d11c1752be240e3761aa Mon Sep 17 00:00:00 2001 From: Vlada Chirmicci Date: Thu, 8 Jan 2026 11:24:36 +0000 Subject: [PATCH 11/11] Remove the applies_switch in favour of listing the options --- .../elasticsearch/circuit-breaker-errors.md | 54 ++++++++++--------- 1 file changed, 28 insertions(+), 26 deletions(-) diff --git a/troubleshoot/elasticsearch/circuit-breaker-errors.md b/troubleshoot/elasticsearch/circuit-breaker-errors.md index 971db90a50..a98f65c417 100644 --- a/troubleshoot/elasticsearch/circuit-breaker-errors.md +++ b/troubleshoot/elasticsearch/circuit-breaker-errors.md @@ -47,32 +47,34 @@ Caused by: org.elasticsearch.common.breaker.CircuitBreakingException: [parent] D **Check circuit breaker statistics** -To get statistics about the circuit breaker per node. Use one of the following: - -::::{applies-switch} - -:::{applies-item} { "stack": "ga" } -Use the [get node statistics](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-nodes-stats) API: - -```console -GET _nodes/stats?filter_path=nodes.*.breakers -``` -::: - -:::{applies-item} { "stack": "ga 9.3" } -Use the [get circuit breakers statistics](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-circuit-breaker) API: -```console -GET /_cat/circuit_breaker/ -``` -::: - -:::: - -The response provides the following information: -- Estimated memory used for the operation. -- Memmory limit for the circuit breaker. -- Total number of times the circuit breaker has been triggered and prevented an out of memory error since node uptime. -- And an overhead which is a constant that all estimates for the circuit breaker are multiplied with to calculate a final estimate. +To get statistics about the circuit breaker per node, use one of the following: + +* You can use the [get node statistics](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-nodes-stats) API: + + ```console + GET _nodes/stats?filter_path=nodes.*.breakers + ``` + + The response provides the following information: + - Estimated memory used for the operation. + - Memory limit for the circuit breaker. + - Total number of times the circuit breaker has been triggered and prevented an out of memory error since node uptime. + - And an overhead which is a constant that all estimates for the circuit breaker are multiplied with to calculate a final estimate. + + +* {applies_to}`stack: ga 9.3` Starting with {{es}} version 9.3, you can use the [get circuit breakers statistics](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-circuit-breaker) API: + + ```console + GET /_cat/circuit_breaker/ + ``` + + This API provides a concise, human-readable tabular output that is useful for quick monitoring and troubleshooting. The response includes the following information for each circuit breaker: + - The circuit breaker name (for example, `request`, `fielddata`, `in_flight_requests`). + - The node ID where the circuit breaker is located. + - Estimated memory currently in use by the circuit breaker. + - Memory limit configured for the circuit breaker. + - Total number of times the circuit breaker has been triggered. + - Overhead factor applied to memory estimates. **Check JVM memory usage**