Dears,
The parameters named: threadpool.XXX.queue_size may control the queue sizes.
But how to read the current (in real time) size/load on those queues to avoid in runtime overloading Elasticsearch and or to see if they are optimally used and the lengths are properly set?
I had tried to find the answer in the CAT API, but there is nothing explicit related to those queues (perhaps I do not see anything).
Thanks in advance and best regards,
Seweryn.