From 84408ee06b5cbe4cfb71f7f8a6ab9f9354cb4195 Mon Sep 17 00:00:00 2001 From: Stef Nestor <26751266+stefnestor@users.noreply.github.com> Date: Fri, 19 Jun 2026 12:59:17 -0600 Subject: [PATCH 1/2] Link watermark blog Add new [watermark blog](https://www.elastic.co/search-labs/blog/elasticsearch-disk-watermark-troubleshooting) from [watermark doc](https://www.elastic.co/docs/troubleshoot/elasticsearch/fix-watermark-errors). --- troubleshoot/elasticsearch/fix-watermark-errors.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/troubleshoot/elasticsearch/fix-watermark-errors.md b/troubleshoot/elasticsearch/fix-watermark-errors.md index 089b6cea9c..62b19e1fb9 100644 --- a/troubleshoot/elasticsearch/fix-watermark-errors.md +++ b/troubleshoot/elasticsearch/fix-watermark-errors.md @@ -51,6 +51,10 @@ The following are some common setup issues leading to watermark errors: * A high number of replicas can quickly multiply storage requirements, as each replica consumes the same disk space as the primary shard. Refer to [Index settings](elasticsearch://reference/elasticsearch/index-settings/index-modules.md) for details. * Oversized shards can make disk usage spikes more likely and slow down recovery and rebalancing. Refer to [Size your shards](/deploy-manage/production-guidance/optimize-performance/size-shards.md#shard-size-recommendation) for guidance. +:::{tip} +For common examples, refer to our blog [Why your Elasticsearch cluster is hitting disk watermarks: 14 real-world causes explained](https://www.elastic.co/search-labs/blog/elasticsearch-disk-watermark-troubleshooting). +::: + ## Monitor disk usage [fix-watermark-errors-monitor] :::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md From 90d6ad7b39332eccdc9fad3e6f1099810201b5d0 Mon Sep 17 00:00:00 2001 From: Stef Nestor <26751266+stefnestor@users.noreply.github.com> Date: Wed, 24 Jun 2026 10:30:35 -0600 Subject: [PATCH 2/2] Apply suggestion from @shainaraskas Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --- troubleshoot/elasticsearch/fix-watermark-errors.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/troubleshoot/elasticsearch/fix-watermark-errors.md b/troubleshoot/elasticsearch/fix-watermark-errors.md index 62b19e1fb9..0fdf003f12 100644 --- a/troubleshoot/elasticsearch/fix-watermark-errors.md +++ b/troubleshoot/elasticsearch/fix-watermark-errors.md @@ -51,9 +51,7 @@ The following are some common setup issues leading to watermark errors: * A high number of replicas can quickly multiply storage requirements, as each replica consumes the same disk space as the primary shard. Refer to [Index settings](elasticsearch://reference/elasticsearch/index-settings/index-modules.md) for details. * Oversized shards can make disk usage spikes more likely and slow down recovery and rebalancing. Refer to [Size your shards](/deploy-manage/production-guidance/optimize-performance/size-shards.md#shard-size-recommendation) for guidance. -:::{tip} -For common examples, refer to our blog [Why your Elasticsearch cluster is hitting disk watermarks: 14 real-world causes explained](https://www.elastic.co/search-labs/blog/elasticsearch-disk-watermark-troubleshooting). -::: +For more causes and remediation guidance, refer to the Elastic blog post [Why your Elasticsearch cluster is hitting disk watermarks](https://www.elastic.co/search-labs/blog/elasticsearch-disk-watermark-troubleshooting). ## Monitor disk usage [fix-watermark-errors-monitor]