Skip to content
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

Reason behind closing all idle connections aggresively #237

Open
pg30 opened this issue Sep 6, 2024 · 0 comments
Open

Reason behind closing all idle connections aggresively #237

pg30 opened this issue Sep 6, 2024 · 0 comments

Comments

@pg30
Copy link

pg30 commented Sep 6, 2024

Hey,
I was trying to understand the flow of Do function and noticed that all idle connections are being closed if we are not able to read the request body or if all retries are exhausted and we still have an error.

Can't we selectively close the current connection that is causing problems rather than closing all the good connections that can be reused for subsequent requests to the same host.

I am trying to understand the reasoning behind this as we are going to integrate this lib in production service with a high throughput and I am uncomfortable with the impact of closing idle connections.

TIA for helping me out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
@pg30 and others