# How to decease bulk queue size?

**URL:** <https://discuss.elastic.co/t/how-to-decease-bulk-queue-size/555>\
**Category:** Elasticsearch\
**Created:** [May 12, 2015, 1:27pm UTC](https://discuss.elastic.co/t/how-to-decease-bulk-queue-size/555 "2015-05-12T13:27:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![chenryn](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chenryn/32/44917_2.png) [@chenryn](https://discuss.elastic.co/u/chenryn)\
**Post date:** [May 12, 2015, 1:27pm UTC](https://discuss.elastic.co/t/how-to-decease-bulk-queue-size/555/1 "2015-05-12T13:27:05Z")

</div>

I find some of nodes were running into max bulk queue. But after I stop all my rsyslog/logstash process, the bulk queue size didn't decease. Some other nodes would even increase its bulk queue size!

I try to get hot\_threads of such node, got only two lucene segment merge thread. (old indices)

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [May 12, 2015, 2:10pm UTC](https://discuss.elastic.co/t/how-to-decease-bulk-queue-size/555/2 "2015-05-12T14:10:03Z")

</div>

Are you sure you are looking at the number of entries in the queue or are  
you looking at the number of threads spun up to handle bulk? Have a look  
at  
[http://www.elastic.co/guide/en/elasticsearch/reference/1.x/modules-threadpool.html](http://www.elastic.co/guide/en/elasticsearch/reference/1.x/modules-threadpool.html)  
for more on these queues.

---

<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, 12:14am UTC](https://discuss.elastic.co/t/how-to-decease-bulk-queue-size/555/3 "2017-07-06T00:14:27Z")

</div>