Fix testLimitConcurrentNodes #132633
Merged
Fix testLimitConcurrentNodes #132633
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
idegtiarenko
added
>test-failure
elasticsearchmachine
added
the
needs:risk
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
dnhatn
approved these changes
Aug 11, 2025
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.
The test is checking that we dispatch 5 requests 2 at the time, however some failures happened observing concurrency of 1.
This could rarely happen when request producer is slower than dispatcher. I was not able to reproduce this.
I think this is less likely to happen if we have more requests. Updating the test to send 10 requests instead of 5.
Closes: #132607