Support max_use and max_lifetime backend parameters#764
Draft
ulyssa wants to merge 1 commit intofastly:mainfrom
Draft
Support max_use and max_lifetime backend parameters#764ulyssa wants to merge 1 commit intofastly:mainfrom
max_use and max_lifetime backend parameters#764ulyssa wants to merge 1 commit intofastly:mainfrom
Conversation
5 tasks
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
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.
Change summary
This is a draft PR for adding support for two different backend fields that are going to be added to the API:
max_use, which specifies how many times an HTTP keepalive connection can be used before it's no longer pooled.max_lifetime, which specifies in milliseconds an upper bound for how long an HTTP keepalive connection can be open before it's no longer used.All Submissions:
New Feature Submissions:
Changes to Core Features:
User Impact
This will allow using a newly exposed feature in both Delivery and Compute, which have added support for honoring these backend parameters in their connection pooling logic.
Are there any considerations that need to be addressed for release?