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

Prevent InfluxDB client from leaking TCP connections #6425

Merged
merged 1 commit into from
Apr 19, 2016
Merged

Conversation

sparrc
Copy link
Contributor

@sparrc sparrc commented Apr 19, 2016

Required for all non-trivial PRs
  • Rebased/mergable
  • CHANGELOG.md updated

If users properly call client.Close(), then this will make sure that
established tcp connections dont continually grow when creating new http
clients.

This fixes the case where users are creating new http clients on top of
existing valid connections.

This was encountered in Telegraf when we were recreating our http
clients after getting write failures that were unrelated to the actual
connection being severed (such as typos in the retention policy, see
influxdata/telegraf#1058)

@jwilder jwilder added this to the 0.13.0 milestone Apr 19, 2016
@jwilder
Copy link
Contributor

jwilder commented Apr 19, 2016

Needs changelog entry, but 👍

If users properly call client.Close(), then this will make sure that
established tcp connections dont continually grow when creating new http
clients.

This fixes the case where users are creating new http clients on top of
existing _valid_ connections.

This was encountered in Telegraf when we were recreating our http
clients after getting write failures that were unrelated to the actual
connection being severed (such as typos in the retention policy, see
influxdata/telegraf#1058)
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.

2 participants