-
Notifications
You must be signed in to change notification settings - Fork 39
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: do not reuse connections per default #105
Conversation
stop reusing connections per default, by modifying the http.Transport DisableKeepAlive field to true per default. Can be overriden through setting KUBENURSE_REUSE_CONNECTIONS env var to "true" Signed-off-by: Clément Nussbaumer <[email protected]>
99f288b
to
47f274a
Compare
@zbindenren @djboris9 what do you think ? the effect on the number of open file descriptor/goroutines is really interesting. the http request duration also starts to be more interesting ! do you agree that this mode should be the default ? |
Signed-off-by: Clément Nussbaumer <[email protected]>
Signed-off-by: Clément Nussbaumer <[email protected]>
47f274a
to
4113065
Compare
Pull Request Test Coverage Report for Build 7584865362
💛 - Coveralls |
Signed-off-by: Clément Nussbaumer <[email protected]>
@clementnuss LGTM 👍 |
the default configuration changes: now kubenurse will NOT reuse connections per default. this permits to have a clearer picture, as closed long-lived connections might not involve DNS resolution, and might hide Load balancer pool problems. Signed-off-by: Clément Nussbaumer <[email protected]>
a0222b8
to
9cb33d7
Compare
stop reusing connections per default, by modifying the http.Transport DisableKeepAlive field to true per default. Can be overriden through setting KUBENURSE_REUSE_CONNECTIONS env var to "true"
This will be a minor change, as the results and behaviour of Kubenurse is modified consequently.