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

Aerospike plugin memory leak #4195

Closed
deric opened this issue May 24, 2018 · 9 comments
Closed

Aerospike plugin memory leak #4195

deric opened this issue May 24, 2018 · 9 comments
Labels
bug unexpected problem or unintended behavior regression something that used to work, but is now broken

Comments

@deric
Copy link
Contributor

deric commented May 24, 2018

Relevant telegraf.conf:

[[inputs.aerospike]]
  servers = ["localhost:3000"]

System info:

  • Debian GNU/Linux 8.10 (jessie)
  • telegraf 1.6.3-1

Steps to reproduce:

  1. Upgrade to 1.6.3
  2. Configure aerospike input

Expected behavior:

Don't leak memory.

Actual behavior:

Leaks memory. A lot. After 24h uptime telegraf occupies 10GB RAM

Additional info:

There was no problem with 1.6.2, quite likely related to changes done in #4127.

cc @TheSAS

@TheSAS
Copy link
Contributor

TheSAS commented May 24, 2018

Sorry.
Seems like it is true (((, i can confirm that memory leak also. Strange that it wasn't spotted while testing that change on test environment.
I'll try to do memory profile using pprof.

@danielnelson danielnelson added bug unexpected problem or unintended behavior regression something that used to work, but is now broken labels May 24, 2018
@danielnelson danielnelson added this to the 1.6.4 milestone May 24, 2018
@shadowlord017
Copy link

Same thing. 1.6.3, aerospike plugin, Ubuntu 16.04

@danielnelson
Copy link
Contributor

I'm planning to do the 1.6.4 release on Monday, it seems that we should revert back to the previous version for now due to the amount of memory being used.

@danielnelson
Copy link
Contributor

I have reverted to the previous version, but lets keep this open until we are able to update.

@zaaraameera2014
Copy link

Tyxhshbjwj

@zaaraameera2014
Copy link

R58HC45JKVD

@deric
Copy link
Contributor Author

deric commented Jul 19, 2018

@danielnelson Currently refactored Gopkg.toml uses version = "^1.33.0" which is going to re-introduce this memory leak.
I'd recommend using

version = "<=1.27.0"

until the issue in aerospike-client-go is resolved.

@danielnelson
Copy link
Contributor

#4462

@danielnelson danielnelson removed this from the 1.6.4 milestone Aug 6, 2019
@sspaink
Copy link
Contributor

sspaink commented Apr 12, 2022

Closing as we are now using a much later version of aerospike and I haven't seen any recent reports about a memory leak.

@sspaink sspaink closed this as completed Apr 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unexpected problem or unintended behavior regression something that used to work, but is now broken
Projects
None yet
Development

No branches or pull requests

7 participants