From 061109a5efb30a33c2d841cf8d23e151746f58b5 Mon Sep 17 00:00:00 2001 From: Stef Nestor <26751266+stefnestor@users.noreply.github.com> Date: Wed, 31 Jul 2024 17:12:20 -0600 Subject: [PATCH] feedback Co-authored-by: David Turner --- .../common-issues/disk-usage-exceeded.asciidoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/reference/troubleshooting/common-issues/disk-usage-exceeded.asciidoc b/docs/reference/troubleshooting/common-issues/disk-usage-exceeded.asciidoc index 369528987ed86..728d805db7a30 100644 --- a/docs/reference/troubleshooting/common-issues/disk-usage-exceeded.asciidoc +++ b/docs/reference/troubleshooting/common-issues/disk-usage-exceeded.asciidoc @@ -8,8 +8,7 @@ When a data node is critically low on disk space and has reached the <>, the following -error is logged: `Error: disk usage exceeded flood-stage watermark, index has -read-only-allow-delete block`. +error is logged: `Error: disk usage exceeded flood-stage watermark, index has read-only-allow-delete block`. To prevent a full disk, when a node reaches this watermark, {es} <> to any index with a shard on the node. If the block affects related system @@ -20,7 +19,7 @@ this could induce {kib}'s `Kibana Server is not Ready yet` {es} will automatically remove the write block when the affected node's disk usage falls below the <>. To achieve this, {es} attempts to rebalance some of the affected node's shards -to other nodes in the same data tier. +to other nodes in the same data tier. [[fix-watermark-errors-rebalance]] ==== Monitor rebalancing