-
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
Fluentd process never exits when blocking for full buffer queue #1260
Comments
@repeatedly will you fix this problem in v0.12 versions? |
@tagomoris Okay, I will check it. |
#1396 fixes this problem for v0.14 or later. |
Released as v0.14.12 |
Fixed in v0.14.12. And v0.12 is now EOL? (No activities until end of 2019 as described in https://www.fluentd.org/blog/drop-schedule-announcement-in-2019) |
v0.12 is not maintained anymore, I'll close it. |
I confirmed this problem on Fluentd v0.12.29, but I know that v0.14.x has this problem too.
When we enable
<buffer> overflow_action block </buffer>
orbuffer_queue_full_action block
and the buffer queue is actually full, input threads will block, and never returns if output plugins doesn't go back to normal.If users will try to stop Fluentd process under this situation, Fluentd don't stop these threads, and the process never stops.
The text was updated successfully, but these errors were encountered: