Fix benchmark system runner no shard available error #2225
Merged
Conversation
This file contains 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
mrodm
changed the title
💚 Build Succeeded
History
cc @mrodm |
jsoriano
approved these changes
Nov 13, 2024
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.
Skip errors related to
no_shard_available_action_exceptionwhen querying to ES to count for documents in benchmarks.To avoid errors like the ones in this build:
https://buildkite.com/elastic/elastic-package/builds/4296#019324f6-874c-448e-8b72-c6b84ae661e8/204-787
This exception/skip is also added when doing searches in Elasticsearch:
elastic-package/internal/testrunner/runners/system/tester.go
Line 712 in 769dc4a
Added temporarily a log message to show that the
no_shards_available_action_exceptionis caught here:https://buildkite.com/elastic/elastic-package/builds/4302#01932566-5526-4a51-b122-4ec779f782ad/194-755