From 23e39aefada8b2c661e61e2cc4ab84d90204058a Mon Sep 17 00:00:00 2001 From: Stef Nestor <26751266+stefnestor@users.noreply.github.com> Date: Thu, 14 Dec 2023 11:17:52 -0700 Subject: [PATCH] [DOC+] Node Stats fs.available reflects XFS quotas MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 👋 howdy, team! Could we include "XFS quotas" as an example for "depending on OS or process level restrictions" for doc searchability for users to better understand how to investigate this potential lever's impact? TIA! Stef --- docs/reference/cluster/nodes-stats.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/cluster/nodes-stats.asciidoc b/docs/reference/cluster/nodes-stats.asciidoc index eacbabb99f045..e2848f9a8e70f 100644 --- a/docs/reference/cluster/nodes-stats.asciidoc +++ b/docs/reference/cluster/nodes-stats.asciidoc @@ -1792,14 +1792,14 @@ Total number of unallocated bytes in all file stores. `available`:: (<>) Total disk space available to this Java virtual machine on all file -stores. Depending on OS or process level restrictions, this might appear +stores. Depending on OS or process level restrictions (e.g. XFS quotas), this might appear less than `free`. This is the actual amount of free disk space the {es} node can utilise. `available_in_bytes`:: (integer) Total number of bytes available to this Java virtual machine on all file -stores. Depending on OS or process level restrictions, this might appear +stores. Depending on OS or process level restrictions (e.g. XFS quotas), this might appear less than `free_in_bytes`. This is the actual amount of free disk space the {es} node can utilise. =======