Skip to content

(Doc+) Expand watermark resolution #119174

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jan 29, 2025
Merged

(Doc+) Expand watermark resolution #119174

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6209be2
(Doc+) Expand watermark resolution
kunisen Dec 20, 2024
927a111
Merge branch 'main' into kunisen-docpr-es-116892
shainaraskas Dec 23, 2024
dfccb27
Apply suggestions from code review
leemthompo Jan 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 25 additions & 10 deletions docs/reference/troubleshooting/common-issues/disk-usage-exceeded.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ GET _cluster/allocation/explain
[[fix-watermark-errors-temporary]]
==== Temporary Relief

To immediately restore write operations, you can temporarily increase the
To immediately restore write operations, you may consider temporarily increasing the
<<disk-based-shard-allocation,disk watermarks>> and remove the
<<index-block-settings,write block>>.

Expand Down Expand Up @@ -102,19 +102,34 @@ PUT _cluster/settings
[[fix-watermark-errors-resolve]]
==== Resolve

As a long-term solution, we recommend you do one of the following best suited
To resolve, we recommend you do one of the following best suited
to your use case:

* add nodes to the affected <<data-tiers,data tiers>>
+
TIP: You should enable <<xpack-autoscaling,autoscaling>> for clusters deployed using our {ess}, {ece}, and {eck} platforms.
* horizontally scale nodes of the affected <<data-tiers,data tiers>>

* upgrade 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`.
* vertically scale existing nodes to increase disk space

* delete unneeded indices using the <<indices-delete-index,delete index API>>
* delete indices using the <<indices-delete-index,delete index API>>, either
permanently if unneeded or temporarily to later
<<snapshots-restore-snapshot,snapshot restore>>

* update related <<index-lifecycle-management,ILM policy>> to push indices
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.
Comment on lines +118 to +124
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we explain why they have to do the deletion here? how does someone determine if this note applies to them?


To avoid this situation, we recommend you do one of the following best
suited to your use case:

* enable <<xpack-autoscaling,autoscaling>> for clusters deployed using our
{ess}, {ece}, and {eck} platforms

* setup {kibana-ref}/kibana-alerts.html[Stack Monitoring Alerts] on top of
<<monitor-elasticsearch-cluster,{es} Monitoring>> to be notified before
flood-stage watermark is reached
Loading