You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
👋 howdy, team!
1. Related to elastic/dev#2631, highlights customers are usually seeking `heap.percent` instead of `ram.percent`
2. Aligns the claimed "(Default)" columns in doc to what returned for v8.15.1 test cluster
Copy file name to clipboardExpand all lines: docs/reference/cat/nodes.asciidoc
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,16 +50,16 @@ Valid columns are:
50
50
(Default) IP address, such as `127.0.1.1`.
51
51
52
52
`heap.percent`, `hp`, `heapPercent`::
53
-
(Default) Maximum configured heap, such as `7`.
53
+
(Default) Used percentage of total allocated Elasticsearch JVM heap, such as `7`. This reflects only the {es} process running within the operating system and is the most direct indicator of its JVM/heap/memory resource performance.
54
54
55
55
`heap.max`, `hm`, `heapMax`::
56
-
(Default) Total heap, such as `4gb`.
56
+
Total heap, such as `4gb`.
57
57
58
58
`ram.percent`, `rp`, `ramPercent`::
59
-
(Default) Used total memory percentage, such as `47`.
59
+
(Default) Used percentage of total operating system's memory, such as `47`. This reflects all processes running on operating system instead of only {es} and is not guaranteed to correlate to its performance.
0 commit comments