-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release/6.0] fix issue where HTTP2 connection could be scavenged but not disposed #62236
Merged
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
Tagging subscribers to this area: @dotnet/ncl Issue DetailsBackport of #62225 to release/6.0 Customer ImpactTestingRisk
|
MihaZupan
approved these changes
Dec 2, 2021
ManickaP
approved these changes
Dec 9, 2021
karelz
approved these changes
Dec 10, 2021
karelz
approved these changes
Dec 10, 2021
@karelz can you please handle tactics mail for this as Im going to be out. |
I'll merge whenever this is approved by tactics. |
leecow
added
Servicing-approved
Approved for servicing release
and removed
Servicing-consider
Issue for next servicing release review
labels
Dec 16, 2021
/azp run runtime |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-libraries enterprise-linux |
Azure Pipelines successfully started running 1 pipeline(s). |
CI failures:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport of #62225 to release/6.0
/cc @stephentoub @geoffkizer
Customer Impact
When scavenging connections, if we end up scavenging at least one HTTP/1.1 connection and at least one HTTP2 connection for the same connection pool (i.e. origin server), the first HTTP2 connection will be removed from the connection list but not disposed, leading to a connection leak.
Having both HTTP/1.1 and HTTP2 connections to the same server is not common, but if this happens the impact is pretty bad.
This is a regression in 6.0.
Testing
Customer provided with private binaries. They confirmed the change works and fixes the issue.
Risk
Very low -- trivial fix.