# Bug : monitoring the "queue\_size" of thread pool is not working on ElasticSearch 5.0.0 (release) **URL:** \ **Category:** Elasticsearch\ **Created:** [October 26, 2016, 9:15am UTC](https://discuss.elastic.co/t/bug-monitoring-the-queue-size-of-thread-pool-is-not-working-on-elasticsearch-5-0-0-release/63979 "2016-10-26T09:15:56Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![opendoc42](https://avatars.discourse-cdn.com/v4/letter/o/7ab992/32.png) [@opendoc42](https://discuss.elastic.co/u/opendoc42)\ **Post date:** [October 26, 2016, 9:15am UTC](https://discuss.elastic.co/t/bug-monitoring-the-queue-size-of-thread-pool-is-not-working-on-elasticsearch-5-0-0-release/63979/1 "2016-10-26T09:15:56Z")
Hello everyone, I try to monitor the thread pool for ElasticSearch 5.0.0-rc1 . I followed the documentation : [https://www.elastic.co/guide/en/elasticsearch/reference/5.0/cat-thread-pool.html](https://www.elastic.co/guide/en/elasticsearch/reference/5.0/cat-thread-pool.html) ``` curl -X GET "http://XXXXXX:9206/_cat/thread_pool/generic?v&h=id,name,size,queue,queue_size,largest,max,active" id name size queue queue_size largest max active 8aGMLBq4SyetuVcft9gcJg generic 4 0 4 128 0 L76JoIgsTnCvZQihzUWCzw generic 5 0 5 128 0 JUTPQum2S-Ot9zqSmwgydQ generic 4 0 5 128 0 ``` However, I do not have the information for the "queue\_size". Could you explain me ? Thank you, Alexandre. ---
**Author:** ![opendoc42](https://avatars.discourse-cdn.com/v4/letter/o/7ab992/32.png) [@opendoc42](https://discuss.elastic.co/u/opendoc42)\ **Post date:** [October 27, 2016, 8:54am UTC](https://discuss.elastic.co/t/bug-monitoring-the-queue-size-of-thread-pool-is-not-working-on-elasticsearch-5-0-0-release/63979/2 "2016-10-27T08:54:02Z")
Hello everyone, Would you have a solution? ElasticSearch 5.0 is now realase, and I would like to use ElasticSearch 5.0 in production. I would have that information. It's a bug? On ES 2.4 it works fine ! ``` curl -X GET "http://X.X.X.X:9205/_cat/thread_pool" X.X.X.X X.X.X.X 0 0 0 0 0 0 0 0 0 X.X.X.X X.X.X.X 0 0 0 0 0 0 0 0 0 X.X.X.X X.X.X.X 0 0 0 0 0 0 0 0 0 ``` Thank you, Alexandre. ---
**Author:** ![opendoc42](https://avatars.discourse-cdn.com/v4/letter/o/7ab992/32.png) [@opendoc42](https://discuss.elastic.co/u/opendoc42)\ **Post date:** [October 27, 2016, 9:12am UTC](https://discuss.elastic.co/t/bug-monitoring-the-queue-size-of-thread-pool-is-not-working-on-elasticsearch-5-0-0-release/63979/3 "2016-10-27T09:12:20Z")
I just tested with the release version 5.0.0 and I have the same problem! ---
**Author:** ![opendoc42](https://avatars.discourse-cdn.com/v4/letter/o/7ab992/32.png) [@opendoc42](https://discuss.elastic.co/u/opendoc42)\ **Post date:** [October 28, 2016, 5:36am UTC](https://discuss.elastic.co/t/bug-monitoring-the-queue-size-of-thread-pool-is-not-working-on-elasticsearch-5-0-0-release/63979/4 "2016-10-28T05:36:33Z")
No idea ? ---
**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:** [October 30, 2016, 12:28pm UTC](https://discuss.elastic.co/t/bug-monitoring-the-queue-size-of-thread-pool-is-not-working-on-elasticsearch-5-0-0-release/63979/5 "2016-10-30T12:28:28Z")
The generic thread pool has a queue only bounded available heap. It'd probably make more sense if we outputted "unbounded" instead of empty string in that column though. So I filed an issue > ---
**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, 10:08pm UTC](https://discuss.elastic.co/t/bug-monitoring-the-queue-size-of-thread-pool-is-not-working-on-elasticsearch-5-0-0-release/63979/6 "2017-07-05T22:08:29Z")