# Scaling Logstash: Redis queue - channels or list?

**URL:** <https://discuss.elastic.co/t/scaling-logstash-redis-queue-channels-or-list/63741>\
**Category:** Logstash\
**Created:** [October 24, 2016, 11:02am UTC](https://discuss.elastic.co/t/scaling-logstash-redis-queue-channels-or-list/63741 "2016-10-24T11:02:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kariboe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kariboe/32/12676_2.png) [@kariboe](https://discuss.elastic.co/u/kariboe)\
**Post date:** [October 24, 2016, 11:02am UTC](https://discuss.elastic.co/t/scaling-logstash-redis-queue-channels-or-list/63741/1 "2016-10-24T11:02:26Z")

</div>

We are in the process of setting up new ELK stack. The idea is to have:

N nodes --\> 2Logstash Shippers --\> Redis (Master/Slave) --\> 2 Logstash Indexers --\> ES cluster --\> Kibana

Only problem we have right now is the configuration/usage of Redis. Should we go for Redis lists or channels?  
Can we define 2 Redis input plugins on the logstash indexers of the data\_type pattern.channel ?? Or should we stay with 1 list (RPUSH/BLPOP) configuration?

I like the idea of having multiple channels to have better management. But does it work with multiple indexers?

Kind regards,

Stefaan

---

<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:33am UTC](https://discuss.elastic.co/t/scaling-logstash-redis-queue-channels-or-list/63741/2 "2017-07-06T04:33:04Z")

</div>

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