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

client: Use sane default values for the custom transport #45

Merged

Conversation

bekriebel
Copy link
Contributor

@bekriebel bekriebel commented Mar 12, 2019

When setting up the custom transport for TLS support, the values for
timeouts, keepalive, and connection counts are all defaulting to zero
values. This can cause the client to not reconnect to a server that has
become unavailable.

Use the values of DefaultTransport in net/http to set up the custom
transport with appropriate settings.

Fixes #46.

When setting up the custom transport for TLS support, the values for
timeouts, keepalive, and connection counts are all defaulting to zero
values. This can cause the client to not reconnect to a server that has
become unavailable.

Use the values of DefaultTransport in net/http to set up the custom
transport with appropriate settings.
@brian-brazil brian-brazil merged commit 2047a5c into prometheus-community:master Mar 13, 2019
@brian-brazil
Copy link
Contributor

Thanks!

giskou pushed a commit to giskou/PushProx that referenced this pull request Apr 8, 2019
…community#45)

When setting up the custom transport for TLS support, the values for
timeouts, keepalive, and connection counts are all defaulting to zero
values. This can cause the client to not reconnect to a server that has
become unavailable.

Use the values of DefaultTransport in net/http to set up the custom
transport with appropriate settings.
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

Successfully merging this pull request may close these issues.

None yet

2 participants