-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Memory leak on connection failures #1857
Comments
Thank you for taking the time to raise this issue. However, it has not had any activity on it in the past 90 days and will be closed in 30 days if no updates occur. |
Not stale, as danielqsj/kafka_exporter#54 still is being updated. I personally have not been able to test this again since my last comment. |
Thank you for taking the time to raise this issue. However, it has not had any activity on it in the past 90 days and will be closed in 30 days if no updates occur. |
Versions
Logs
Following logs also have
&b.opened
values along with the already present log message to highlight the issue.logs: CLICK ME
Problem Description
The way atomic has been used to track connections, it leaks memory on connection timeouts and potentially other failures as well. I have noticed this while debugging increasing memory usage for kafka exporter which uses sarama
this seems to be the cause as it simply keeps using up memory space for new connections and is not cleared which is troubling in the case of failed connections.
Thanks!
The text was updated successfully, but these errors were encountered: