-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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 (outputs.opensearch ??) #16295
Comments
@bg4erem thanks for your report and your investigations! Could you try to test your setup by replacing the Could you please also check the Telegraf log to see if there is any hint for an issue?!? |
Hi Sven @srebhan |
Thanks @bg4erem! After a quick glance, this seems to be related to the "bulk indexer" handling in the code. I have to read deeper into this... One thing you can try is to reduce the As the team is out during Christmas and only be back on Jan 13th, I will take a look as soon as I'm back... |
Hi @srebhan ! Thank you. I set |
Thanks a lot @bg4erem! Will take a look as soon as I'm back. |
Relevant telegraf.conf
Logs from Telegraf
System info
Ubuntu 22.04 LTS, Telegraf 1.33 (earlier version of Telegraf had the same issue for me)
Docker
No response
Steps to reproduce
Expected behavior
Stable work with adequate system resources consumption
Actual behavior
After Telegraf start-up, it consumes 130 MB of memory. In my measurement, after 15 min memory usage grows up to 4 GB, eventually causing OOM later when taking all available memory.
Additional info
The text was updated successfully, but these errors were encountered: