-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
worker-0 randomly SIGKILLed #3413
Comments
Probably same with #3341 |
Don't worry, the comment is just only for add a reference to the similar issue. |
I checked implementation but fluentd itself doesn't send I think #3341 is also killed by OOM killer, because gracefulReload consumes more memory. A known methods to reduce fluentd's memory usage is using jemalloc (3.x is better). |
I'm not familiar with detailed your environment, but you use Fluentd somethings as kubernetes Fluentd operator and set limits of resources for CPU and memory? |
BTW the detail of my above explanations was wrong.: - Fluent::Engine
+ Fluent::RootAgent Lines 167 to 202 in 5bc4c6b
|
@ashie and @cosmo0920 Thanks for all the details. I have now implemented jemalloc 3.6.0 and will monitor memory utilization of the fluentd pods to make sure they are not killed by Kubernetes OOM killer. |
Thanks for the information. For high load environment, using jemalloc 3.6.0 is better for memory consumption than using jemalloc 5.2.1 and plain Linux malloc, right? |
As I mentioned before, we think it's triggered by OOM killer, the cause is high memory usage. |
Describe the bug
We noticed in the fluentd logs that worker-0 was SIGKILLed for no apparent reason. Right before the SIGKILL, there were messages about tailing logs that no longer exist because k8s pods were deleted, so maybe that has something to do with it.
To Reproduce
Not sure, but can try having fluentd tail k8s pods logs and constantly create/delete pods.
Expected behavior
worker-0 shouldn't get SIGKILLed for no apparent reason.
Your Environment
Fluentd or td-agent version: fluentd
1.12.3
.Operating system:
Ubuntu 20.04.1 LTS
Kernel version:
5.4.0-62-generic
Your Configuration
Your Error Log
The text was updated successfully, but these errors were encountered: