# Monitoring Bulk Request Queue

**URL:** <https://discuss.elastic.co/t/monitoring-bulk-request-queue/44117>\
**Category:** Elasticsearch\
**Created:** [March 11, 2016, 7:08am UTC](https://discuss.elastic.co/t/monitoring-bulk-request-queue/44117 "2016-03-11T07:08:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [March 11, 2016, 7:08am UTC](https://discuss.elastic.co/t/monitoring-bulk-request-queue/44117/1 "2016-03-11T07:08:56Z")

</div>

Hi,  
Is there a way to view the number of bulk requests waiting to be processed? It will help me to understand whether I have "threadpool.bulk.queue\_size" set appropriately...

Regards,  
David

---

<div class="post-metadata">

**Author:** ![rusty](https://avatars.discourse-cdn.com/v4/letter/r/f17d59/32.png) [@rusty](https://discuss.elastic.co/u/rusty)\
**Post date:** [March 11, 2016, 8:47am UTC](https://discuss.elastic.co/t/monitoring-bulk-request-queue/44117/2 "2016-03-11T08:47:24Z")

</div>

Hi! Try this simple linux shell script:  
`watch -d -n 5 "curl -s 'localhost:9200/_cat/thread_pool?v&h=ip,port,ra,rq,fa,fq,sa,sq,gea,geq,ga,gq,maa,maq,fma,fmq,bs,br,ba,bq' | sort"`

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 11, 2016, 11:25pm UTC](https://discuss.elastic.co/t/monitoring-bulk-request-queue/44117/3 "2016-03-11T23:25:43Z")

</div>

> [@dawiro](#):
>
> It will help me to understand whether I have "threadpool.bulk.queue\_size" set appropriately.

We don't recommend changing this for a number of reasons.  
If you're threadpools are filling up then it's best to find out why, rather than just increase them.

---

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [March 14, 2016, 9:58am UTC](https://discuss.elastic.co/t/monitoring-bulk-request-queue/44117/4 "2016-03-14T09:58:04Z")

</div>

Well, I've been seeing the beats input blocking on a congested logstash pipeline. Those events are associated with RemoteTransportExceptions in elasticsearch. In logstash, the elasticsearch output workers are set to 2 and flush\_size is set to 500.  
Other references I've seen to this type of log ingestion problem suggest raising the bulk.queue\_size parameter...

---

<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 5, 2017, 11:08pm UTC](https://discuss.elastic.co/t/monitoring-bulk-request-queue/44117/5 "2017-07-05T23:08:42Z")

</div>