-
Notifications
You must be signed in to change notification settings - Fork 191
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
Various fixes for managed transport #637
Conversation
486e8ba
to
08c3490
Compare
The experimental managed transport can also leverage TransportPool, moving it to its own package to accommodate that use case. Signed-off-by: Paulo Gomes <[email protected]>
Ensure all requests are completely processed and closed, to prove odds of the underlying connections to be reused. The transport now is pooled and reused whenever possible. Signed-off-by: Paulo Gomes <[email protected]>
Signed-off-by: Paulo Gomes <[email protected]>
Signed-off-by: Paulo Gomes <[email protected]>
Signed-off-by: Paulo Gomes <[email protected]>
08c3490
to
a78338a
Compare
To test the fixes, you must opt-in to the managed transport by setting the environment variable Use one of temporary images below or build from this PR:
Note that managed transport only works with the |
The underlying SSH connections are kept open and are reused across several SSH sessions. This is due to upstream issues in which concurrent/parallel SSH connections may lead to instability. golang/go#51926 golang/go#27140 Signed-off-by: Paulo Gomes <[email protected]>
a78338a
to
92ad1f8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Great work on investigating and fixing all the issues.
Resolves some known issues:
And also improve overall observability.