# Logstash circuit breaker triggered but marvel monitoring metrics seems OK

**URL:** <https://discuss.elastic.co/t/logstash-circuit-breaker-triggered-but-marvel-monitoring-metrics-seems-ok/35093>\
**Category:** Logstash\
**Created:** [November 19, 2015, 10:30pm UTC](https://discuss.elastic.co/t/logstash-circuit-breaker-triggered-but-marvel-monitoring-metrics-seems-ok/35093 "2015-11-19T22:30:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![maxhyjal](https://avatars.discourse-cdn.com/v4/letter/m/ac8455/32.png) [@maxhyjal](https://discuss.elastic.co/u/maxhyjal)\
**Post date:** [November 19, 2015, 10:30pm UTC](https://discuss.elastic.co/t/logstash-circuit-breaker-triggered-but-marvel-monitoring-metrics-seems-ok/35093/1 "2015-11-19T22:30:45Z")

</div>

I've run into this prior to 2.0 and after I upgrade the Elasticsearch and Logstash stack to 2.0, is there a good way to get around this?

Keep getting those in logstash.log  
message=\>"Lumberjack input: The circuit breaker has detected a slowdown or stall in the pipeline, the input is closing the current connection and rejecting new connection until the pipeline recover.", :exception=\>LogStash::CircuitBreaker::HalfOpenBreaker, :level=\>:warn}  
{:timestamp=\>"2015-11-19T21:49:50.388000+0000", :message=\>"CircuitBreaker::rescuing exceptions", :name=\>"Lumberjack input", :exception=\>LogStash::SizedQueueTimeout::TimeoutError, :level=\>:warn}  
{:timestamp=\>"2015-11-19T21:49:50.388000+0000", :message=\>"Lumberjack input: The circuit breaker has detected a slowdown or stall in the pipeline, the input is closing the current connection and rejecting new connection until the pipeline recover.", :exception=\>LogStash::CircuitBreaker::HalfOpenBreaker, :level=\>:warn}  
{:timestamp=\>"2015-11-19T21:49:50.718000+0000", :message=\>"Lumberjack input: the pipeline is blocked, temporary refusing new connection.", :level=\>:warn}

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 20, 2015, 3:40am UTC](https://discuss.elastic.co/t/logstash-circuit-breaker-triggered-but-marvel-monitoring-metrics-seems-ok/35093/2 "2015-11-20T03:40:25Z")

</div>

This happens because downstream is overloaded.  
Are you monitoring your stack?

---

<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 6, 2017, 5:22am UTC](https://discuss.elastic.co/t/logstash-circuit-breaker-triggered-but-marvel-monitoring-metrics-seems-ok/35093/3 "2017-07-06T05:22:02Z")

</div>

Closed on July 6, 2017, 5:22am UTC