Add server-side validation to prevent index.refresh_interval values…
#245542
+108
−11
Conversation
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
… less than 5s in serverless
Contributor
|
🤖 Jobs for this PR can be triggered through checkboxes. 🚧
ℹ️ To trigger the CI, please tick the checkbox below 👇
|
rStelmach
changed the title
index.refresh_interval values…index.refresh_interval values…
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
https://github.com/elastic/observability-error-backlog/issues/325
Summary
This PR fixes an issue where setting a short
index.refresh_interval(e.g.,1s) in Serverless caused an "Failed to execute Elasticsearch actions" error.Problem
Serverless Elasticsearch enforces a minimum refresh interval of
5s(or-1to disable). Kibana's Streams plugin was not validating the value of this setting, only ensuring the key was allowed. This caused valid-looking changes to fail asynchronously during the execution plan phase.Testing
validate_stream.test.tscovering valid (5s,1m,-1) and invalid (1s,4s) scenarios.