IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Nodes hot threads API
editNodes hot threads API
editReturns the hot threads on each selected node in the cluster.
Description
editThis API yields a breakdown of the hot threads on each selected node in the cluster. The output is plain text with a breakdown of each node’s top hot threads.
Path parameters
edit-
<node_id>
- (Optional, string) Comma-separated list of node IDs or names used to limit returned information.
Query parameters
edit-
ignore_idle_threads
- (Optional, Boolean) If true, known idle threads (e.g. waiting in a socket select, or to get a task from an empty queue) are filtered out. Defaults to true.
-
interval
-
(Optional, time units) The interval to do the second
sampling of threads. Defaults to
500ms
. -
snapshots
-
(Optional, integer) Number of samples of thread stacktrace. Defaults to
10
. -
threads
-
(Optional, integer) Specifies the number of hot threads to provide
information for. Defaults to
3
. -
master_timeout
-
(Optional, time units) Specifies the period of time to wait for
a connection to the master node. If no response is received before the timeout
expires, the request fails and returns an error. Defaults to
30s
. -
timeout
-
(Optional, time units) Specifies the period of time to wait for
a response. If no response is received before the timeout expires, the request
fails and returns an error. Defaults to
30s
. -
type
-
(Optional, string) The type to sample. Available options are
block
,cpu
, andwait
. Defaults tocpu
.
Examples
editGET /_nodes/hot_threads GET /_nodes/nodeId1,nodeId2/hot_threads