Repository navigation
Fix the disk watermark example in ISM error resolutions - #13346
Merged
kolchfa-aws merged 2 commits intoOct 19, 2026
Merged
Conversation
The "The index is blocked" resolution suggested raising only the low disk watermark to "25.0gb". OpenSearch rejects that request twice over: fractional byte values are not accepted, and a byte value for `low` cannot be combined with the default percentage values of `high` and `flood_stage`. Raising `low` would also not remove the read-only-allow-delete block, which follows the flood-stage watermark. Raise all three watermarks with the same unit, and note that the block is released automatically once disk usage falls below the high watermark. Signed-off-by: YoungjuKim <[email protected]>
fjvbn2003
requested review from
cwperks,
dlvenable,
epugh,
kolchfa-aws,
peterzhuamazon and
sumobrian
as code owners
October 16, 2026 17:11
|
Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Merged. Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer. When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). |
Signed-off-by: Fanit Kolchina <[email protected]>
kolchfa-aws
approved these changes
Oct 19, 2026
kolchfa-aws
left a comment
kolchfa-aws
left a comment
Collaborator
There was a problem hiding this comment.
Thank you, @fjvbn2003! Updated to show both byte and percentage versions. LGTM
kolchfa-aws
added a commit
that referenced
this pull request
Oct 19, 2026
) * Fix the disk watermark example in ISM error resolutions The "The index is blocked" resolution suggested raising only the low disk watermark to "25.0gb". OpenSearch rejects that request twice over: fractional byte values are not accepted, and a byte value for `low` cannot be combined with the default percentage values of `high` and `flood_stage`. Raising `low` would also not remove the read-only-allow-delete block, which follows the flood-stage watermark. Raise all three watermarks with the same unit, and note that the block is released automatically once disk usage falls below the high watermark. * Update to show both versions --------- (cherry picked from commit 24d0c62) Signed-off-by: YoungjuKim <[email protected]> Signed-off-by: Fanit Kolchina <[email protected]> Signed-off-by: opensearch-ci-bot <[email protected]> Co-authored-by: Youngju KIM <[email protected]> Co-authored-by: Fanit Kolchina <[email protected]>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
The ISM error resolutions page's section "The index is blocked" tells readers to raise the low disk watermark with this request:
The request fails, and the advice behind it would not work either:
25.0gbis rejected:Failed to parse bytes value [25.0gb]. Fractional bytes values have been deprecated since Legacy 6.2.25gbis also rejected, becausehighandflood_stageare still percentages (the defaults):unable to consistently parse [...low=25gb], [...high=90%], and [...flood_stage=95%] as percentage or bytes(DiskThresholdSettings.doValidate).read-only-allow-deleteblock is applied when a node exceeds the flood-stage watermark, andDiskThresholdMonitorreleases it automatically once the node is below the high watermark. Raisinglowdoes neither. When the node is already over the flood stage, raisinglowalone is rejected anyway (low disk watermark [90%] more than high disk watermark [10%]in the test below).This PR replaces the example with one that raises
low,high, andflood_stagetogether using the same unit. It also adds one sentence about the automatic release and resetting the watermarks tonullafterward.How I tested it
I used a single-node OpenSearch 3.8.0 container (security disabled,
cluster.routing.allocation.disk.watermark.enable_for_single_data_node=true). To simulate a full disk, I set all three watermarks to10%on a node at about 50% disk usage:wm-testgetsindex.blocks.read_only_allow_delete: true. Indexing a document returns429 cluster_block_exception ... disk usage exceeded flood-stage watermark."low": "25.0gb")400, fractional bytes"low": "25gb"400, inconsistent percentage/bytes"low": "90%"alone400,low disk watermark [90%] more than high disk watermark [10%]200. The block is removed within about 9 s, and indexing succeeds again.null200I also ran the exact JSON block from the updated page (nested form,
90%/95%/97%) against the same node. It returnedacknowledged: true.Issues Resolved
None. This is a doc fix and I did not open a separate issue.
Version
all
Frontend features
N/A
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.
This change was drafted with AI assistance (Claude Code) and reviewed by me.
🤖 Generated with Claude Code