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

Scalyr agent memory leak #1311

Open
ManishJain-TomTom opened this issue Nov 13, 2024 · 1 comment
Open

Scalyr agent memory leak #1311

ManishJain-TomTom opened this issue Nov 13, 2024 · 1 comment

Comments

@ManishJain-TomTom
Copy link

Hi Team,

We are using Scalyr in our K8s environment, and found that one of the scalyr agent is constantly using more and more memory.

Screenshot 2024-11-13 at 14 03 57

We are using helm chart version 0.2.45 and scalyr version 2.2.16.

From the release logs of https://github.com/scalyr/scalyr-agent-2/releases/tag/v2.2.16, we saw the number of threads have been changed to 16. Could this be the reason for the increase in memory usage?

Is there a way to limit this, we are planning to set the "syslog_processing_thread_count":"4" to rectify the issue, but wanted to confirm if that is going to have some other side-effects that we should keep an eye on?

@oleg-s1
Copy link

oleg-s1 commented Nov 13, 2024

@ManishJain-TomTom Before this change in 2.2.16 threads count was unlimited.
Setting syslog_processing_thread_count":"4" will limit the usage of memory by syslog monitor definitely, but if only it was really caused by syslog monitor.
Do you use syslog monitor in this agent configuration? Because if not, then modification of this parameter will not make any difference.
There could be something else behind the memory leak then.
We can open support ticket and troubleshoot memory leak if you would like to.

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

No branches or pull requests

2 participants