# Logstash InsertingToQueueTakeTooLong error message

**URL:** <https://discuss.elastic.co/t/logstash-insertingtoqueuetaketoolong-error-message/49477>\
**Category:** Logstash\
**Created:** [May 8, 2016, 7:49am UTC](https://discuss.elastic.co/t/logstash-insertingtoqueuetaketoolong-error-message/49477 "2016-05-08T07:49:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nateuni](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nateuni/32/8512_2.png) [@nateuni](https://discuss.elastic.co/u/nateuni)\
**Post date:** [May 8, 2016, 7:49am UTC](https://discuss.elastic.co/t/logstash-insertingtoqueuetaketoolong-error-message/49477/1 "2016-05-08T07:49:57Z")

</div>

I have been using this pipeline for weeks no issue, today I log on, fire everything up and I am not getting this error message in Logstash:

{:timestamp=\>"2016-05-08T07:43:12.806000+0000", :message=\>"CircuitBreaker::rescuing exceptions", :name=\>"Beats input", :exception=\>LogStash::Inputs::Beats::InsertingToQueueTakeTooLong, :level=\>:warn}  
{:timestamp=\>"2016-05-08T07:43:12.807000+0000", :message=\>"Beats 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::Inputs::BeatsSupport::CircuitBreaker::HalfOpenBreaker, :level=\>:warn}

The only way I can get it to run is to remove all the filters. There has never been an issue before. Everything is running on different EC2 instances. Any idea what would be causing this all of a sudden?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [May 8, 2016, 7:42pm UTC](https://discuss.elastic.co/t/logstash-insertingtoqueuetaketoolong-error-message/49477/2 "2016-05-08T19:42:21Z")

</div>

It looks like you're simply trying to stuff more data into Logstash than it can cope with. Is there any reason to suspect that this isn't just a capacity issue (that can be addressed with more horsepower and/or configuration tuning)?

---

<div class="post-metadata">

**Author:** ![nateuni](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nateuni/32/8512_2.png) [@nateuni](https://discuss.elastic.co/u/nateuni)\
**Post date:** [May 9, 2016, 2:42am UTC](https://discuss.elastic.co/t/logstash-insertingtoqueuetaketoolong-error-message/49477/3 "2016-05-09T02:42:53Z")

</div>

It never was a problem until now, which is odd. But since posting this and doing some reading, I made the change so that the filters is done post Kafka, that way Logstash doesn't lag out.

Thanks.

---

<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, 4:58am UTC](https://discuss.elastic.co/t/logstash-insertingtoqueuetaketoolong-error-message/49477/4 "2017-07-06T04:58:45Z")

</div>

Closed on July 6, 2017, 4:58am UTC