# Elasticsearch circuit break when snapshot is being taken

**URL:** <https://discuss.elastic.co/t/elasticsearch-circuit-break-when-snapshot-is-being-taken/246552>\
**Category:** Elasticsearch\
**Created:** [August 27, 2020, 5:56am UTC](https://discuss.elastic.co/t/elasticsearch-circuit-break-when-snapshot-is-being-taken/246552 "2020-08-27T05:56:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Faiz\_Ahmed\_Mushtak\_H](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/faiz_ahmed_mushtak_h/32/47387_2.png) [@Faiz\_Ahmed\_Mushtak\_H](https://discuss.elastic.co/u/Faiz_Ahmed_Mushtak_H)\
**Post date:** [August 27, 2020, 5:56am UTC](https://discuss.elastic.co/t/elasticsearch-circuit-break-when-snapshot-is-being-taken/246552/1 "2020-08-27T05:56:43Z")

</div>

We have a 10 node elasticsearch cluster (7.2.0) with the following config

```auto
-Xms8gb -- (16gb RAM)
-Xmx8gb
-XX:+UseG1GC
-XX:G1ReservePercent=25
-XX:InitiatingHeapOccupancyPercent=30

```

What we are observing is, occassionally the circuit starts tripping right at the time when our snapshot cron runs (there's a good amount of spike in outgoing network activity as well)

Clearly from the graphs, the heap usage indeed goes upto 7.9gb. We haven't tweaked any circuit settings

We did try reducing the snapshot\_bytes\_per\_sec, but no luck. We also tried reducing the snapshot frequency down to 1hr but that also hasn't helped

We do plan to increase the heap size, unfortunately we are already at 50% usage & this is something elasticseach doesnt recommend. The other option is vertical scaling our instance which is only going to waste our resources unfortunately because this is a low traffic cluster

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 27, 2020, 6:00am UTC](https://discuss.elastic.co/t/elasticsearch-circuit-break-when-snapshot-is-being-taken/246552/2 "2020-08-27T06:00:41Z")

</div>

What is the output of the [cluster stats API](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-stats.html)? Which version are you using?

---

<div class="post-metadata">

**Author:** ![Faiz\_Ahmed\_Mushtak\_H](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/faiz_ahmed_mushtak_h/32/47387_2.png) [@Faiz\_Ahmed\_Mushtak\_H](https://discuss.elastic.co/u/Faiz_Ahmed_Mushtak_H)\
**Post date:** [August 27, 2020, 6:05am UTC](https://discuss.elastic.co/t/elasticsearch-circuit-break-when-snapshot-is-being-taken/246552/3 "2020-08-27T06:05:39Z")

</div>

I don't have cluster stats as of now. we use 7.2.0 elasticsearch

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 27, 2020, 6:07am UTC](https://discuss.elastic.co/t/elasticsearch-circuit-break-when-snapshot-is-being-taken/246552/4 "2020-08-27T06:07:30Z")

</div>

Without the cluster stats I have limited insights into the state of the cluster so I will have a look once you can provide these.

---

<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:** [September 24, 2020, 6:07am UTC](https://discuss.elastic.co/t/elasticsearch-circuit-break-when-snapshot-is-being-taken/246552/5 "2020-09-24T06:07:46Z")

</div>

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