# Circuit\_breaking\_exception

**URL:** <https://discuss.elastic.co/t/circuit-breaking-exception/113693>\
**Category:** Elasticsearch\
**Created:** [January 1, 2018, 12:39pm UTC](https://discuss.elastic.co/t/circuit-breaking-exception/113693 "2018-01-01T12:39:13Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![karthik\_s1](https://avatars.discourse-cdn.com/v4/letter/k/73ab20/32.png) [@karthik\_s1](https://discuss.elastic.co/u/karthik_s1)\
**Post date:** [January 1, 2018, 12:39pm UTC](https://discuss.elastic.co/t/circuit-breaking-exception/113693/1 "2018-01-01T12:39:13Z")

</div>

We are having the following cluster setup

1 master node  
2 client nodes  
2 data nodes

**Master node:**  
8 Gb RAM  
Heap: -Xms2g -Xmx2g

**Each Client nodes:**  
16 Gb RAM  
Heap: -Xms8g -Xmx8g

**Each Data node**  
16 Gb RAM  
Heap: -Xms8g -Xmx8g

Elasticsearch version: 5.2.0

we are pushing data from mysql to elasticsearch through logstash. logstash is configured to use one es-client (lets call it es-client-2). Once this setup was ready it worked for a nearly a week before it started throwing the following issue:

`[INFO][o.e.d.z.ZenDiscovery] [es-client-2] failed to send join request to master [{es-master}{zQzKnjSETXuavCd0OXVv9A}{bUMt-luHQpOfHwAFo1DmMg}{es-master}{10.20.10.40:9300}], reason [RemoteTransportException[[es-master][10.20.10.40:9300][internal:discovery/zen/join]]; nested: IllegalStateException[failure when sending a validation request to node]; nested: RemoteTransportException[[es-client-2][10.20.10.81:9300][internal:discovery/zen/join/validate]]; nested: CircuitBreakingException[[parent] Data too large, data for [<transport_request>] would be larger than limit of [5988548608/5.5gb]]; ]`

Once i restarted this client, it joined the cluster and started working as normal.

I am trying to find the root cause of this issue. Why would it reach a limit of 5.5 gb. At the same time if i try with the other es client, it works.

Can you throw some light on this issue?

---

<div class="post-metadata">

**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\
**Post date:** [January 1, 2018, 2:51pm UTC](https://discuss.elastic.co/t/circuit-breaking-exception/113693/2 "2018-01-01T14:51:15Z")

</div>

Versions less than 5.2.2 had a leak in circuit breaker accounting that could occur with certain clients. Please upgrade to at least 5.2.2 to see if your problem is addressed by this bug fix: [#23310](https://github.com/elastic/elasticsearch/pull/23310).

---

<div class="post-metadata">

**Author:** ![karthik\_s1](https://avatars.discourse-cdn.com/v4/letter/k/73ab20/32.png) [@karthik\_s1](https://discuss.elastic.co/u/karthik_s1)\
**Post date:** [January 2, 2018, 5:43am UTC](https://discuss.elastic.co/t/circuit-breaking-exception/113693/3 "2018-01-02T05:43:41Z")

</div>

Thanks @jasontedor, we will try it out.

---

<div class="post-metadata">

**Author:** ![karthik\_s1](https://avatars.discourse-cdn.com/v4/letter/k/73ab20/32.png) [@karthik\_s1](https://discuss.elastic.co/u/karthik_s1)\
**Post date:** [January 4, 2018, 12:31pm UTC](https://discuss.elastic.co/t/circuit-breaking-exception/113693/4 "2018-01-04T12:31:50Z")

</div>

@jasontedor i have one more question.

Till we faced this issue for the first time, all our inserts and upserts were working fine. once this issue started appearing we are missing some upserts. Does this issue affect upserts in any manner? We are having this doubt, as there had been no change in the application/ elasticsearch cluster configuration during that period.

---

<div class="post-metadata">

**Author:** ![karthik\_s1](https://avatars.discourse-cdn.com/v4/letter/k/73ab20/32.png) [@karthik\_s1](https://discuss.elastic.co/u/karthik_s1)\
**Post date:** [January 5, 2018, 7:26am UTC](https://discuss.elastic.co/t/circuit-breaking-exception/113693/5 "2018-01-05T07:26:00Z")

</div>

@jasontedor May i know your opinion on this?

---

<div class="post-metadata">

**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\
**Post date:** [January 5, 2018, 9:41pm UTC](https://discuss.elastic.co/t/circuit-breaking-exception/113693/6 "2018-01-05T21:41:46Z")

</div>

The issue I referenced should not have any impact on upserts specifically, only that requests in general would be rejected once the circuit breaker has tripped.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 2, 2018, 9:41pm UTC](https://discuss.elastic.co/t/circuit-breaking-exception/113693/7 "2018-02-02T21:41:50Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
