# Logstash not procession all events in custom output plugin

**URL:** https://discuss.elastic.co/t/logstash-not-procession-all-events-in-custom-output-plugin/186179
**Category:** Logstash
**Created:** [June 18, 2019, 5:44am UTC](https://discuss.elastic.co/t/logstash-not-procession-all-events-in-custom-output-plugin/186179 "2019-06-18T05:44:54Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Ram\_Sharan\_Mittal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ram_sharan_mittal/32/47018_2.png) [@Ram\_Sharan\_Mittal](https://discuss.elastic.co/u/Ram_Sharan_Mittal)
#### Post date: [June 18, 2019, 5:44am UTC](https://discuss.elastic.co/t/logstash-not-procession-all-events-in-custom-output-plugin/186179/1 "2019-06-18T05:44:54Z")

</div>

there is an output HTTP custom plugin with wokers\_not\_supported in logstash 2.4 which didn't implement multi\_recieve and get input from a lot of files input. I am seeing only a few file input going but not all. But after putting multi\_recieve it starts working.

Why this is happening because of custom HTTP output plugin, is it single worker of output getting too many calls from input and king of hang?

---

<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 16, 2019, 5:44am UTC](https://discuss.elastic.co/t/logstash-not-procession-all-events-in-custom-output-plugin/186179/2 "2019-07-16T05:44:58Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.