Return 404 for missing indices in cluster health API instead of RED w… #19201
+15
−20
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
This PR Changes the behaviour of the cluster health API when a non-existing-index is requested.
Previously, the API would wait until timeout and returns RED status of cluster
With this change, the API now immediately throws
IndexNotFoundException
, which maps to HTTP 404.Related Issues
Resolves #19022
Check List
ClusterHealthIT
to expectIndexNotFoundException
instead ofRED
for missing indices.ClusterStateHealthTests
to validate immediate 404 behavior.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.