outbound: add additional backend configuration#204
Merged
hawkw merged 3 commits intoalex/outboundfrom Feb 27, 2023
Merged
Conversation
adleong
approved these changes
Feb 27, 2023
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently, the proxy's client policy module supports configuring queue
parameters (capacity and failfast timeout) and load balancer parameters
(the load estimate and peak EWMA parameters) on a per-backend basis.
However, the proxy API does not currently provide these configurations.
This branch adds new messages and fields describing these configurations
to the
outbound.Backendmessage. I chose to nest all the new messagetypes inside of
Backend, but we could also move them out ofBackendif we might want to use them elsewhere.