-
Notifications
You must be signed in to change notification settings - Fork 199
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 #230
Comments
Thanks for your report. Do you think you can provide a memory profile using pprof to help us track the issue down? |
@khaf Sure, after 4min:
|
Telegraf v1.6.3 (git: release-1.6 890f1d3a)
|
After 16min:
|
Do you think there's an easy way for me to setup telegraph to test this myself? A link to a documentation will also help. It would also help if you state your setup: What version of Aerospike Server, Edition and number of nodes. |
Just grab a package from release page and configure aerospike input in
then test cofiguration with:
Probably no outputs are needed, but I haven't tested that. We're using Aerospike |
Mine setup is:
Outputs should be added, you can use:
|
I can't reproduce this issue (anymore). Monitoring telegraph's memory via |
@khaf which version of Telegraf do you use? The bug is present only in |
@deric sorry it seems I missed the github notification in my mail. I just downloaded the latest version from github and compiled it. I noticed the code had the latest version of the client already in, and didn't suffer any memory leaks. Do you still see any in the latest telegraph / aerospike version? |
@kahf as you can see in telegraf#4128:
Obviously you won't see any problems in the latest version, as it uses old If you wanna reproduce the issue, please download |
Downloading the pre-compiled version won't help me much, since I need to compile to be able to both reproduce and then Are you using the prebuilt versions of the telegraph? Could you try building it from source yourself with the latest go client to see if the memory leak is still there? I tried it with the latest client and I couldn't reproduce. |
It's enough to checkout
|
The issue was most likely introduced between v1.27..v1.28 |
I'm in trouble with client-go 1.31.0, which is consuming huge amount of memory around handling "Connection". @deric
|
This seems to have been caused by the addition and default value of |
I'm closing this issue since it is fixed. Feel free to reopen or file a new issue. |
After updating
aerospike-client-go
telegraf started leaking memory inaerospike
plugin (influxdata/telegraf#4195). The cause is probably related to changes done in between1.25.0
and1.32.0
.The text was updated successfully, but these errors were encountered: