# Logstash-forwarder queuing support

**URL:** <https://discuss.elastic.co/t/logstash-forwarder-queuing-support/2129>\
**Category:** Logstash\
**Created:** [June 8, 2015, 12:00pm UTC](https://discuss.elastic.co/t/logstash-forwarder-queuing-support/2129 "2015-06-08T12:00:33Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![tlog](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tlog/32/559_2.png) [@tlog](https://discuss.elastic.co/u/tlog)\
**Post date:** [June 8, 2015, 12:00pm UTC](https://discuss.elastic.co/t/logstash-forwarder-queuing-support/2129/1 "2015-06-08T12:00:33Z")

</div>

Hello all,

in [https://github.com/elastic/logstash-forwarder/issues/18](https://github.com/elastic/logstash-forwarder/issues/18) we see the issue is closed, therefore I thought, redis support is now included in 0.4.0. But how can redis as target being configured?

The config like this

```
output {
  redis {
    host => "INDEXER_HOSTNAME"
    data_type => "list"
    key => "logstash"
    codec => json
  }

```

seems to be only for real logstash not logstash forwarder.

If redis support is still not implemented, can sb please provide examples for another MQ which could buffer the messages ?

Thanks for your help in advance.  
T.

---

<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:** [June 8, 2015, 1:58pm UTC](https://discuss.elastic.co/t/logstash-forwarder-queuing-support/2129/2 "2015-06-08T13:58:09Z")

</div>

logstash-forwarder does not support Redis. Why do you need to submit messages to Redis? There are probably valid reasons for desiring this but there are also reasons based on misconceptions.

---

<div class="post-metadata">

**Author:** ![tlog](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tlog/32/559_2.png) [@tlog](https://discuss.elastic.co/u/tlog)\
**Post date:** [June 8, 2015, 5:17pm UTC](https://discuss.elastic.co/t/logstash-forwarder-queuing-support/2129/3 "2015-06-08T17:17:41Z")

</div>

Hi Magnus,

I need to submit messages to a queuing service like redis or any other MQ, as sometimes logstash needs to be restarted or I get "Lumberjack input, maximum connection exceeded, new connection are rejected.", which all remain on CLOSE\_WAIT!  
Currently I run logstash with "-w 12" which seems to resolve the issue but what happens if the process again stops to receive messages from my forwardes?

Best regards,  
T

---

<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:** [June 8, 2015, 8:14pm UTC](https://discuss.elastic.co/t/logstash-forwarder-queuing-support/2129/4 "2015-06-08T20:14:03Z")

</div>

logstash-forwarder should back off and retry and the messages should eventually arrive (if not then it's a bug). As long as this overload condition is temporary you should be okay. If Logstash _constantly_ pushes back you have an unstable system and chances are that it would fall over even with a message broker inbetween.

---

<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:38am UTC](https://discuss.elastic.co/t/logstash-forwarder-queuing-support/2129/5 "2017-07-06T05:38:07Z")

</div>

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