-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
output buffer files never closed (witk kafka_buffered_output) #1688
Comments
I first heard this problem. |
Yes, kafka receives all data. Buffer files are empty. Currently i switched to memory buffers to avoid this problem. |
Is empty file above |
BTW, do you edit td-agent related files? |
I seeing this behaviour too:
kafka configuration:
|
This issue has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days |
This issue was automatically closed because of stale in 30 days |
Hi, I'm using fluentd in_tail plugin to follow logs from docker containers on kubernetes node. Logs are send to kafka topics. When using kafka_buffered_output with file buffers, buffer file handlers are not closed (and buffer files are not removed) until fluentd restart. Even when source file does not longer exist. This leads to increased number of open file handlers (expecially when lots of containers is created and removed).
td-agent version td-agent-2.3.5-1.el7.x86_64
fluent-plugin-kafka gem version 0.5.5
OS CentOS Linux release 7.3.1611 (Core)
My fluent config
Opened file handlers
Even when app container is removed (input file for in_tail does is removed), output buffers for kafka are kept open, which eventually leads to exceeding number of open file handlers per process/OS.
The text was updated successfully, but these errors were encountered: