-
Notifications
You must be signed in to change notification settings - Fork 309
Fluentd on K8s stopped flushing logs to Elastic #732
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Could you use Simple Sniffer class to get rid of firing siniffer feature on Elasticsearch client? |
@cosmo0920 Thanks for your reply! Isn't using ElasticsearchSimpleSniffer equivalent to disabling reload functionality via |
Yes. If you don't use it, Elasticsearch client fires sniffer request in every 10000 bulk request. This is not related to |
This came from this line, and Elasticsearch client seems triger only when and also other place, Elasticsearch client may trigger reload_connection with sniffer class is Sniffer class is not evaluated if host reload(https://github.com/elastic/elasticsearch-ruby/blob/f877b6cb7fe905b1492120213947dc60afbdacc8/elasticsearch-transport/lib/elasticsearch/transport/transport/base.rb#L85) is not triggered, and I can find just above 2 places which may trigger host reload, that's why if Actually I investigate this issue, and I found root cause, so could you check it out ? |
#733 is merged. This should be closed. |
Uh oh!
There was an error while loading. Please reload this page.
(check apply)
Problem
We have Fluentd running in Daemonset (using fluentd-kubernetes-daemonset).
At some point almost all instances of Fluentd stop flushing their queue.
I checked related issues like #525 and rancher/rancher#25819 and #600, but no luck.
Elastic is behind load balancer, so we set following setting:
No errors or warning messages appears in fluentd logs.
I checked lsof: buffer and queue files are opened by ruby process:
Growing queue (there're much more files on other instances):
There're connections to destination host
10.32.150.166:12000
, but no traffic:Steps to replicate
fluentd.conf
Expected Behavior or What you need to ask
...
Using Fluentd and ES plugin versions
fluent-gem list
,td-agent-gem list
or your Gemfile.lockThe text was updated successfully, but these errors were encountered: