Implement limited per-second hedging #41
Closed
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.
This PR is an upstreaming of an implementation we have within Grafana Labs.
We need to restrict the number of hedged requests on a per-process level, in order to prevent large bursts of hedged requests when we hit the upstream service's limits and all requests start to become slow.
I've imported a dependency, which I believe violates one of the features, but I believe in this case it is warranted and the dependency can be trusted (it's an experimental package from the Go team, and may be upstreamed into the stdlib later).
I still need to write docs for usage, but wanted to get your thoughts on this first.
Credit to @cyriltovena for the initial implementation.