(Doc+) Expand watermark resolution #116892
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,40 @@ | ||
| ++++ | ||
| <div class="tabs" data-tab-group="host"> | ||
| <div role="tablist" aria-label="Fix watermark issue"> | ||
| <button role="tab" | ||
| aria-selected="true" | ||
| aria-controls="cloud-tab-watermark" | ||
| id="cloud-watermark"> | ||
| Elasticsearch Service | ||
| </button> | ||
| <button role="tab" | ||
| aria-selected="false" | ||
| aria-controls="self-managed-tab-watermark" | ||
| id="self-managed-watermark" | ||
| tabindex="-1"> | ||
| Self-managed | ||
| </button> | ||
| </div> | ||
| <div tabindex="0" | ||
| role="tabpanel" | ||
| id="cloud-tab-watermark" | ||
| aria-labelledby="cloud-watermark"> | ||
| ++++ | ||
|
|
||
| include::troubleshooting-watermark.asciidoc[tag=cloud] | ||
|
|
||
| ++++ | ||
| </div> | ||
| <div tabindex="0" | ||
| role="tabpanel" | ||
| id="self-managed-tab-watermark" | ||
| aria-labelledby="self-managed-watermark" | ||
| hidden=""> | ||
| ++++ | ||
|
|
||
| include::troubleshooting-watermark.asciidoc[tag=self-managed] | ||
|
|
||
| ++++ | ||
| </div> | ||
| </div> | ||
| ++++ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| // tag::cloud[] | ||
|
|
||
| * {ref}/docs-delete.html[Delete unused data]. | ||
| * {cloud}/ec-customize-deployment-components.html[Increase the disk size on your Hot data and Content tier (scale up)] | ||
|
|
||
| NOTE: If your {es} cluster is unhealthy and reports a status of red, then increasing the disk size of your Hot data and Content tier may fail. You might need to delete some data so the configuration can be edited. If you want to increase your disk size without deleting data, then {cloud}/ec-get-help.html[reach out to Elastic support] and we will assist you with scaling up. | ||
|
|
||
| Also, for future prevention, you can do below: | ||
|
|
||
| * {cloud}/ec-customize-deployment-components.html[Increase the disk size on your Hot data and Content tier (scale up)] | ||
|
There was a problem hiding this comment. It's invalid to restrict this to only hot/content tier, it can happen on any data tier, here and above |
||
| * Enable <<xpack-autoscaling,autoscaling>> for clusters deployed using our {ess}, {ece}, and {eck} platforms. | ||
| * Update related <<index-lifecycle-management,ILM policy>> to push indices through to later <<data-tiers,data tiers>> | ||
|
|
||
| // end::cloud[] | ||
|
|
||
| // tag::self-managed[] | ||
| As a long-term solution, we recommend you do one of the following best suited | ||
| to your use case: | ||
|
|
||
| * Add nodes to the affected <<data-tiers,data tiers>> | ||
| * Upgrade existing nodes to increase disk space | ||
| * Delete unneeded indices using the <<indices-delete-index,delete index API>> | ||
| * Update related <<index-lifecycle-management,ILM policy>> to push indices through to later <<data-tiers,data tiers>> | ||
|
|
||
| // end::self-managed[] | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We usually recommend deleting per index not doc otherwise you don't quickly clean out disk.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah thanks @stefnestor WDYT we use this one?
https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-delete-index.html
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, that's the one I linked below 🙂