# Workers option logstash input

**URL:** https://discuss.elastic.co/t/workers-option-logstash-input/43358
**Category:** Logstash
**Created:** [March 3, 2016, 9:20am UTC](https://discuss.elastic.co/t/workers-option-logstash-input/43358 "2016-03-03T09:20:15Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![Bruno\_Lavoie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bruno_lavoie/32/8408_2.png) [@Bruno\_Lavoie](https://discuss.elastic.co/u/Bruno_Lavoie)
#### Post date: [March 10, 2016, 2:26pm UTC](https://discuss.elastic.co/t/workers-option-logstash-input/43358/9 "2016-03-10T14:26:46Z")

</div>

Also, I have written a question about tuning this redis parameter with the new NG-Pipeline as of 2.2.

> [@Input-redis parameters versus pipeline parameters](https://discuss.elastic.co/t/input-redis-parameters-versus-pipeline-parameters/43948):
>
> Hello, As of 2.2, pipeline architecture has changed. From the docs: Each input {} statement in the Logstash configuration file runs in its own thread. Inputs write events to a common Java SynchronousQueue. This queue holds no events, instead transferring each pushed event to a free worker, blocking if all workers are busy. Each pipeline worker thread takes a batch of events off this queue, creating a buffer per worker, runs the batch of events through the configured filters, then runs the fi…

It may be of interest to you.

Good luck  
Bruno Lavoie

---

_[View the full topic](https://discuss.elastic.co/t/workers-option-logstash-input/43358)._