management: confirm server-side filtering 404s #18265
Open
+59
−25
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.
Release notes
What does this PR do?
When Central Management is looking up the instance's assigned pipelines, it now confirms a 404 is in fact an empty assignment, differentiating it from a 404 emitted for other reasons.
Why is it important/What is the impact to the user?
An ES node leaving the cluster can emit a 404, indicating that it cannot satisfy the request, which is different than an indication that the list of pipelines is empty.
This fix prevents such a 404 from shutting down the running pipelines.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files (and/or docker env variables)How to test this PR locally
Related issues