# Recv-Q with \> 380K segments waiting to be processed by logstash

**URL:** <https://discuss.elastic.co/t/recv-q-with-380k-segments-waiting-to-be-processed-by-logstash/378579>\
**Category:** Logstash\
**Tags:** docker\
**Created:** [May 27, 2025, 10:14am UTC](https://discuss.elastic.co/t/recv-q-with-380k-segments-waiting-to-be-processed-by-logstash/378579 "2025-05-27T10:14:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![pepitogrillo](https://avatars.discourse-cdn.com/v4/letter/p/dc4da7/32.png) [@pepitogrillo](https://discuss.elastic.co/u/pepitogrillo)\
**Post date:** [May 27, 2025, 10:14am UTC](https://discuss.elastic.co/t/recv-q-with-380k-segments-waiting-to-be-processed-by-logstash/378579/1 "2025-05-27T10:14:21Z")

</div>

Hi All,  
I am currently in a Docker swarm setup with 7 nodes ingesting 20K 200 bytes TPS .  
Recv-Q is at almost 4.000.000 segments waiting to be processed by logstash  
right now I have 80 workers, batch\_size=1000 and pool\_max=5000.  
Have been tweaking server's TCP buffers but there is no much difference.  
Read backpressure can go as high as 50, output write backpressure is low 2-4.  
Any ideas to accelerate ingestion so Recv-Q is lowered?  
Thank you very much  
Daniel