-
Notifications
You must be signed in to change notification settings - Fork 866
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
Reuse connections for 5xx errors #5607
Conversation
Hi @zoewangg, I am working on an AWS SDK Http client based on pekko here, and the only failing test from Luckily I stumbled upon this PR, and I am just wondering why this functionality is being reverted? |
Hi @jtjeferreira, we are still evaluating the change. The main reason is that closing connections for 5xx errors could cause more TCP connection establishment in the unlikely event of outage, which could add request latency and add more load on the server side. In general, we try to keep custom logic in the SDK minimal and let the server side decide if a connection should be kept open or not. |
b9165da
to
b8a4171
Compare
b8a4171
to
0cd9322
Compare
Quality Gate passedIssues Measures |
Motivation and Context
Reuse connections for 5xx errors for all supported HTTP clients. This change reverts #1768 and #2960