Bug : monitoring the "queue_size" of thread pool is not working on ElasticSearch 5.0.0 (release)


(Alex) #1

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

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.


(Alex) #2

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.


(Alex) #3

I just tested with the release version 5.0.0 and I have the same problem!


(Alex) #4

No idea ?


(Nik Everett) #5

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


(system) #6