github-mirrors/elasticsearch
1
0
Fork 0
mirror of https://github.com/elastic/elasticsearch.git synced 2025-06-29 01:44:36 -04:00
Code Issues Projects Releases Packages Wiki Activity

(Doc+) Expand watermark resolution (#119174)

Browse source 
* (Doc+) Expand watermark resolution

Relaunch https://github.com/elastic/elasticsearch/pull/116892 since the original one seems to be outdated and hard to update branch.

* Apply suggestions from code review

Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>

---------

Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
This commit is contained in:
Kuni Sen 2025-01-30 03:31:50 +09:00 • committed by GitHub
parent c0f3024c3f
commit a0f1856a40
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 25 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

36
docs/reference/troubleshooting/common-issues/disk-usage-exceeded.asciidoc
View file

@ -57,7 +57,7 @@ GET _cluster/allocation/explain
[[fix-watermark-errors-temporary]] [[fix-watermark-errors-temporary]]
==== Temporary Relief ==== Temporary Relief
To immediately restore write operations, you can temporarily increase the To immediately restore write operations, you can temporarily increase
<<disk-based-shard-allocation,disk watermarks>> and remove the <<disk-based-shard-allocation,disk watermarks>> and remove the
<<index-block-settings,write block>>. <<index-block-settings,write block>>.
@ -106,19 +106,33 @@ PUT _cluster/settings
[[fix-watermark-errors-resolve]] [[fix-watermark-errors-resolve]]
==== Resolve ==== Resolve
As a long-term solution, we recommend you do one of the following best suited To resolve watermark errors permanently, perform one of the following actions:
to your use case:
* add nodes to the affected <<data-tiers,data tiers>> * Horizontally scale nodes of the affected <<data-tiers,data tiers>>.
+
TIP: You should enable <<xpack-autoscaling,autoscaling>> for clusters deployed using our {ess}, {ece}, and {eck} platforms.
* upgrade existing nodes to increase disk space * Vertically scale existing nodes to increase disk space.
+
TIP: On {ess}, https://support.elastic.co[Elastic Support] intervention may
become necessary if <<cluster-health,cluster health>> reaches `status:red`.
* delete unneeded indices using the <<indices-delete-index,delete index API>> * Delete indices using the <<indices-delete-index,delete index API>>, either
permanently if the index isn't needed, or temporarily to later
<<snapshots-restore-snapshot,restore>>.
* update related <<index-lifecycle-management,ILM policy>> to push indices * update related <<index-lifecycle-management,ILM policy>> to push indices
through to later <<data-tiers,data tiers>> through to later <<data-tiers,data tiers>>
TIP: On {ess} and {ece}, indices may need to be temporarily deleted via
its {cloud}/ec-api-console.html[Elasticsearch API Console] to later
<<snapshots-restore-snapshot,snapshot restore>> in order to resolve
<<cluster-health,cluster health>> `status:red` which will block
{cloud}/ec-activity-page.html[attempted changes]. If you experience issues
with this resolution flow on {ess}, kindly reach out to
https://support.elastic.co[Elastic Support] for assistance.
== Prevent watermark errors
To avoid watermark errors in future, , perform one of the following actions:
* If you're using {ess}, {ece}, or {eck}: Enable <<xpack-autoscaling,autoscaling>>.
* Set up {kibana-ref}/kibana-alerts.html[stack monitoring alerts] on top of
<<monitor-elasticsearch-cluster,{es} monitoring>> to be notified before
the flood-stage watermark is reached.