# Circuit Breaker not triggered even after parent circuit breaker limit is exceeded

**URL:** <https://discuss.elastic.co/t/circuit-breaker-not-triggered-even-after-parent-circuit-breaker-limit-is-exceeded/175804>\
**Category:** Elasticsearch\
**Created:** [April 8, 2019, 9:07am UTC](https://discuss.elastic.co/t/circuit-breaker-not-triggered-even-after-parent-circuit-breaker-limit-is-exceeded/175804 "2019-04-08T09:07:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sagark1992](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sagark1992/32/43647_2.png) [@sagark1992](https://discuss.elastic.co/u/sagark1992)\
**Post date:** [April 8, 2019, 9:07am UTC](https://discuss.elastic.co/t/circuit-breaker-not-triggered-even-after-parent-circuit-breaker-limit-is-exceeded/175804/1 "2019-04-08T09:07:40Z")

</div>

**Cluster information**

- ES Version: 5.1
- Nodes: 3
- Indices: 3
- Total Size: 100GB
- Total Docs: 55 million
- Shards: 5 P and 1 R (for each indices). Total: 40 shards
- Service: AWS ES (SaaS)

**Background** : Our system has a peak point in the morning when we receive high amount of searches, read and write requests which can last up to 10 hours.

**UseCase** : I wanted to force a garbage collection before the peak time. For this, I am updating the cluster settings of the parent circuit breaker

`indices.breaker.total.limit: "55%"`[**Reference**](https://www.elastic.co/guide/en/elasticsearch/guide/current/_limiting_memory_usage.html#_limiting_memory_usage)

**Problem** : But even after the JVM grew from 53% to 56% as you can see in the node stats below, JVM was not garbage collected.

**GET /\_nodes/stats/jvm**

```auto
        "timestamp": 1554375659658,
        "uptime_in_millis": 10960191290,
        "mem": {
          "heap_used_in_bytes": 601959488,
          "heap_used_percent": 56,
          "heap_committed_in_bytes": 1065025536,
          "heap_max_in_bytes": 1065025536,
          "non_heap_used_in_bytes": 243082744,
          "non_heap_committed_in_bytes": 251510784,
          "pools": {
            "young": {
              "used_in_bytes": 11959328,
              "max_in_bytes": 69795840,
              "peak_used_in_bytes": 69795840,
              "peak_max_in_bytes": 69795840
            },
            "survivor": {
              "used_in_bytes": 1260248,
              "max_in_bytes": 8716288,
              "peak_used_in_bytes": 8716288,
              "peak_max_in_bytes": 8716288
            },
            "old": {
              "used_in_bytes": 588739912,
              "max_in_bytes": 986513408,
              "peak_used_in_bytes": 739896688,
              "peak_max_in_bytes": 986513408
            }
          }
        }

```

I don't know if this is a problem at the end of AWS ElasticSearch service or native ES.  
If there is any other way to force a garbage collection I could try that, but I was not able to find any other way to trigger garbage collection.

---

<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:** [May 6, 2019, 9:07am UTC](https://discuss.elastic.co/t/circuit-breaker-not-triggered-even-after-parent-circuit-breaker-limit-is-exceeded/175804/2 "2019-05-06T09:07:40Z")

</div>

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