-
Notifications
You must be signed in to change notification settings - Fork 187
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
Fix obscure HTTP CONNECT goroutine leak #270
Fix obscure HTTP CONNECT goroutine leak #270
Conversation
Hi @jveski. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@cheftako your comments have been addressed - please re-review whenever you're able |
/ok-to-test |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cheftako, jveski The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The connection chan is not closed for DIAL_RSP, which means http handler goroutines stall if the agent fails to dial. This probably went unnoticed because the client connections close as expected and it takes a very long time for enough goroutines to pile up and consume noticeable resources.
To reproduce, just generate a few thousand connections through the tunnel while watching the go_goroutines metric.