-
Notifications
You must be signed in to change notification settings - Fork 25.6k
(Doc+) Resolve watermark on Cloud via Autoscaling #115990
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.
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
Conversation
Expands resolve watermark guide [on ES](https://www.elastic.co/guide/en/elasticsearch/reference/master/fix-watermark-errors.html#fix-watermark-errors-resolve) with the residual content [from ESS](https://www.elastic.co/guide/en/cloud/current/ec-scenario_why_are_shards_unavailable.html?edit#ec-disk-full).
Documentation preview: |
@stefnestor please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation. |
Pinging @elastic/es-docs (Team:Docs) |
docs/reference/troubleshooting/common-issues/disk-usage-exceeded.asciidoc
Outdated
Show resolved
Hide resolved
💔 Backport failedThe backport operation could not be completed due to the following error:
You can use sqren/backport to manually backport by running |
(cherry picked from commit e2bbee1)
(cherry picked from commit e2bbee1)
💔 Some backports could not be created
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
(cherry picked from commit e2bbee1) Co-authored-by: Stef Nestor <[email protected]>
(cherry picked from commit e2bbee1) Co-authored-by: Stef Nestor <[email protected]>
Expands resolve watermark guide on ES with the residual content from ESS. (Goal after will be to remove content ESS-side and leave ES-side as source of truth.) CC: @kunisen