Add feedback

Signed-off-by: Naarcha-AWS <naarcha@amazon.com>
This commit is contained in:
Naarcha-AWS 2022-05-18 12:54:11 -05:00
parent bde449d48a
commit 6b2042745e
2 changed files with 5 additions and 6 deletions

View File

@ -56,12 +56,12 @@ GET /_nodes/data:true/stats
### Order of resolution mechanisms
The order of resolution mechanisms is applied sequentially, and each can add or remove nodes. The following examples means yield different results:
The order of resolution mechanisms is applied sequentially, and each can add or remove nodes. The following examples yield different results:
If you want to get statistics from all the nodes but the cluster-manager node, use:
If you want to get statistics from all the nodes but the cluster manager node, use:
```bash
GET /_nodes/_all,cluster_namager:false/stats
GET /_nodes/_all,cluster_manager:false/stats
```
However, if we switch the resolution mechanisms, then the result will include all the cluster nodes including the cluster manager node.

View File

@ -8,8 +8,7 @@ nav_order: 10
# Nodes hot threads
This REST API provide information about busy JVM threads for selected cluster nodes.
It provides a unique view of what activity each node spends time on.
The nodes hot threads endpoint provides information about busy JVM threads for selected cluster nodes. It provides a unique view of the of activity each node.
## Example
@ -40,7 +39,7 @@ timeout | TimeValue | A request [timeout](../index/#timeout). Defaults to `30s`.
## Response
Unlike majority of OpenSearch API responses, this response is in a text format.
Unlike the majority of OpenSearch API responses, this response is in a text format.
It consists of one section per each cluster node included in the response.