thread_pool command shows cluster wide thread pool statistics per node. By default the active, queue and rejected
statistics are returned for all thread pools.
Which looks like:
node-0 bulk 0 0 0 node-0 fetch_shard_started 0 0 0 node-0 fetch_shard_store 0 0 0 node-0 flush 0 0 0 node-0 force_merge 0 0 0 node-0 generic 0 0 0 node-0 get 0 0 0 node-0 index 0 0 0 node-0 listener 0 0 0 node-0 management 1 0 0 node-0 refresh 0 0 0 node-0 search 0 0 0 node-0 snapshot 0 0 0 node-0 warmer 0 0 0
The first column is the node name
The second column is the thread pool name
name bulk fetch_shard_started fetch_shard_store flush force_merge generic get index listener management refresh search snapshot warmer
The next three columns show the active, queue, and rejected statistics for each thread pool
active queue rejected 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
The cat thread pool API accepts a
thread_pool_patterns URL parameter for specifying a
comma-separated list of regular expressions to match thread pool names.
which looks like:
id name active rejected completed 0EWUhXeBQtaVGlexUeVwMg generic 0 0 70
Here the host columns and the active, rejected and completed suggest thread pool statistics are displayed.
All built-in thread pools and custom thread pools are available.
Thread Pool Fieldsedit
For each thread pool, you can load details about it by using the field names in the table below.
The current (*) type of thread pool (
The number of active threads in the current thread pool
The number of threads in the current thread pool
The number of tasks in the queue for the current thread pool
The maximum number of tasks permitted in the queue for the current thread pool
The number of tasks rejected by the thread pool executor
The highest number of active threads in the current thread pool
The number of tasks completed by the thread pool executor
The configured minimum number of active threads allowed in the current thread pool
The configured maximum number of active threads allowed in the current thread pool
The configured keep alive time for threads
In addition to details about each thread pool, it is also convenient to get an
understanding of where those thread pools reside. As such, you can request
other details like the
ip of the responding node(s).
The unique node ID
The ephemeral node ID
The process ID of the running node
The hostname for the current node
The IP address for the current node
The bound transport port for the current node