Fix IndexRecoveryIT#testSourceThrottling #110044
Merged
+4
−1
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
Ensure that the target node has a high enough recovery max bytes per second to avoid any accidental throttling. Closes elastic#110026
fcofdez
added
>test
|
Pinging @elastic/es-distributed (Team:Distributed) |
|
I couldn't reproduce the test failure but in the two failures that I looked into the target node had a "low" recovery max bytes per second setting ( ) so my suspicion is that the source node gets the setting update first and sends enough data to cause a small throttle in the target node before it updates its recovery max bytes per second. |
arteam
approved these changes
Jun 21, 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.
Ensure that the target node has a high enough recovery max bytes per second to avoid any accidental throttling.
Closes #110026