# Testing different circuitbreakers

**URL:** <https://discuss.elastic.co/t/testing-different-circuitbreakers/236934>\
**Category:** Elasticsearch\
**Created:** [June 12, 2020, 6:57pm UTC](https://discuss.elastic.co/t/testing-different-circuitbreakers/236934 "2020-06-12T18:57:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dinesh\_gnanasamy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dinesh_gnanasamy/32/63402_2.png) [@dinesh\_gnanasamy](https://discuss.elastic.co/u/dinesh_gnanasamy)\
**Post date:** [June 12, 2020, 6:57pm UTC](https://discuss.elastic.co/t/testing-different-circuitbreakers/236934/1 "2020-06-12T18:57:02Z")

</div>

I am trying to test various circuitbreakers to gain better understanding for tuning various `breaker` `limits` .. for example, for tuning `indices.breaker.request.limit` on a cluster with 50% indexing and 50% querying load characteristics, what type of indexing operations can be simulated to trigger request circuitbreaker.

Often, during recovery of heavy shards or heavy scroll-based queries, I have always noticed parent circuitbreaker tripping. But have never observed individual breakers tripping.

I am using Elasticsearch 7.0.1 and heap allocation is around 14Gb per node and I use a 3 node cluster

Thanks in advance

- Dinesh

---

<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:** [July 10, 2020, 6:59pm UTC](https://discuss.elastic.co/t/testing-different-circuitbreakers/236934/2 "2020-07-10T18:59:49Z")

</div>

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