Make querier_sharding_test less brittle #4970
Merged
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.
I am guessing that by increasing number of queries (sample space), we are less likely to deviated from the assertion of
require.InDelta(t, 0, diff, numQueries*0.20)
.By empirical data, if I start more than 100 queries concurrently, I get HTTP 429 error; so I implemented some batching logic on top of the original
numQueries
. I have tuned bunch of config in Cortex and could not get rid of the HTTP 429, so I came to believe the 429 may be caused by the file description issue mentioned in the original comment.Signed-off-by: Alvin Lin [email protected]