WARNING: Version 2.3 of Elasticsearch has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
cat nodes
editcat nodes
editThe nodes command shows the cluster topology.
% curl 192.168.56.10:9200/_cat/nodes SP4H 4727 192.168.56.30 9300 2.3.4 1.8.0_73 72.1gb 35.4 93.9mb 79 239.1mb 0.45 3.4h d m Boneyard _uhJ 5134 192.168.56.10 9300 2.3.4 1.8.0_73 72.1gb 33.3 93.9mb 85 239.1mb 0.06 3.4h d * Athena HfDp 4562 192.168.56.20 9300 2.3.4 1.8.0_73 72.2gb 74.5 93.9mb 83 239.1mb 0.12 3.4h d m Zarek
The first few columns tell you where your nodes live. For sanity it also tells you what version of ES and the JVM each one runs.
nodeId pid ip port version jdk u2PZ 4234 192.168.56.30 9300 2.3.4 1.8.0_73 URzf 5443 192.168.56.10 9300 2.3.4 1.8.0_73 ActN 3806 192.168.56.20 9300 2.3.4 1.8.0_73
The next few give a picture of your heap, memory, and load.
diskAvail heapPercent heapMax ramPercent ramMax load 72.1gb 31.3 93.9mb 81 239.1mb 0.24 72.1gb 19.6 93.9mb 82 239.1mb 0.05 72.2gb 64.9 93.9mb 84 239.1mb 0.12
The last columns provide ancillary information that can often be useful when looking at the cluster as a whole, particularly large ones. How many master-eligible nodes do I have? How many client nodes? It looks like someone restarted a node recently; which one was it?
uptime data/client master name 3.5h d m Boneyard 3.5h d * Athena 3.5h d m Zarek
Columns
editBelow is an exhaustive list of the existing headers that can be
passed to nodes?h= to retrieve the relevant details in ordered
columns. If no headers are specified, then those marked to Appear
by Default will appear. If any header is specified, then the defaults
are not used.
Aliases can be used in place of the full header name for brevity.
Columns appear in the order that they are listed below unless a
different order is specified (e.g., h=pid,id versus h=id,pid).
When specifying headers, the headers are not placed in the output
by default. To have the headers appear in the output, use verbose
mode (v). The header name will match the supplied value (e.g.,
pid versus p). For example:
% curl 192.168.56.10:9200/_cat/nodes?v&h=id,ip,port,v,m id ip port version m pLSN 192.168.56.30 9300 2.3.4 m k0zy 192.168.56.10 9300 2.3.4 m 6Tyi 192.168.56.20 9300 2.3.4 * % curl 192.168.56.10:9200/_cat/nodes?h=id,ip,port,v,m pLSN 192.168.56.30 9300 2.3.4 m k0zy 192.168.56.10 9300 2.3.4 m 6Tyi 192.168.56.20 9300 2.3.4 *
| Header | Alias | Appear by Default | Description | Example |
|---|---|---|---|---|
|
|
No |
Unique node ID |
k0zy |
|
|
No |
Process ID |
13061 |
|
|
Yes |
Host name |
n1 |
|
|
Yes |
IP address |
127.0.1.1 |
|
|
No |
Bound transport port |
9300 |
|
|
No |
Elasticsearch version |
2.3.4 |
|
|
No |
Elasticsearch Build hash |
5c03844 |
|
|
No |
Running Java version |
1.8.0 |
|
|
No |
Available disk space |
1.8gb |
|
|
No |
Used heap |
311.2mb |
|
|
Yes |
Used heap percentage |
7 |
|
|
No |
Maximum configured heap |
1015.6mb |
|
|
No |
Used total memory |
513.4mb |
|
|
Yes |
Used total memory percentage |
47 |
|
|
No |
Total memory |
2.9gb |
|
|
No |
Used file descriptors |
123 |
|
|
Yes |
Used file descriptors percentage |
1 |
|
|
No |
Maximum number of file descriptors |
1024 |
|
|
No |
Most recent load average |
0.22 |
|
|
No |
Node uptime |
17.3m |
|
|
Yes |
Data node (d); Client node (c) |
d |
|
|
Yes |
Current master (*); master eligible (m) |
m |
|
|
Yes |
Node name |
Venom |
|
|
No |
Size of completion |
0b |
|
|
No |
Used fielddata cache memory |
0b |
|
|
No |
Fielddata cache evictions |
0 |
|
|
No |
Used query cache memory |
0b |
|
|
No |
Query cache evictions |
0 |
|
|
No |
Used request cache memory |
0b |
|
|
No |
Request cache evictions |
0 |
|
|
No |
Request cache hit count |
0 |
|
|
No |
Request cache miss count |
0 |
|
|
No |
Number of flushes |
1 |
|
|
No |
Time spent in flush |
1 |
|
|
No |
Number of current get operations |
0 |
|
|
No |
Time spent in get |
14ms |
|
|
No |
Number of get operations |
2 |
|
|
No |
Time spent in successful gets |
14ms |
|
|
No |
Number of successful get operations |
2 |
|
|
No |
Time spent in failed gets |
0s |
|
|
No |
Number of failed get operations |
1 |
|
|
No |
Number of current deletion operations |
0 |
|
|
No |
Time spent in deletions |
2ms |
|
|
No |
Number of deletion operations |
2 |
|
|
No |
Number of current indexing operations |
0 |
|
|
No |
Time spent in indexing |
134ms |
|
|
No |
Number of indexing operations |
1 |
|
|
No |
Number of current merge operations |
0 |
|
|
No |
Number of current merging documents |
0 |
|
|
No |
Size of current merges |
0b |
|
|
No |
Number of completed merge operations |
0 |
|
|
No |
Number of merged documents |
0 |
|
|
No |
Size of current merges |
0b |
|
|
No |
Time spent merging documents |
0s |
|
|
No |
Number of current percolations |
0 |
|
|
No |
Memory used by current percolations |
0b |
|
|
No |
Number of registered percolation queries |
0 |
|
|
No |
Time spent percolating |
0s |
|
|
No |
Total percolations |
0 |
|
|
No |
Number of refreshes |
16 |
|
|
No |
Time spent in refreshes |
91ms |
|
|
No |
Total script compilations |
17 |
|
|
No |
Total compiled scripts evicted from cache |
6 |
|
|
No |
Current fetch phase operations |
0 |
|
|
No |
Time spent in fetch phase |
37ms |
|
|
No |
Number of fetch operations |
7 |
|
|
No |
Open search contexts |
0 |
|
|
No |
Current query phase operations |
0 |
|
|
No |
Time spent in query phase |
43ms |
|
|
No |
Number of query operations |
9 |
|
|
No |
Open scroll contexts |
2 |
|
|
No |
Time scroll contexts held open |
2m |
|
|
No |
Completed scroll contexts |
1 |
|
|
No |
Number of segments |
4 |
|
|
No |
Memory used by segments |
1.4kb |
|
|
No |
Memory used by index writer |
18mb |
|
|
No |
Maximum memory index writer may use before it must write buffered documents to a new segment |
32mb |
|
|
No |
Memory used by version map |
1.0kb |