Masahiro Nakagawa

Results 253 comments of Masahiro Nakagawa

> You could create a variable to store the last log name and lock it behind a mutex so threads can set & access it safely. I think this has...

For avoiding HEAD request call, set `check_object false`. In addition. you need to change `s3_object_key_format` to use `%{uuid_flush}` or `${chunk_id}` for unique path.

We have a plan to replace poseidon with ruby-kafka. After replaced that, we will consider it.

> What could be the cause of fluentd keeping those connections alive until timeout? fluent-plugin-kafka uses ruby-kafka library internally so it depends on ruby-kafka's setting. out_kafka plugin is for testing...

> Can u advise? What the advise do you want? How to reduce TCP_WAITS or other?

Interesting. out_kafka2 and out_kafka_buffered uses same approches and behaviour should be same. I will check out_kafka2 code.

Please paste your configuration here. I checked mongo driver and it seems to delete closed socket: https://github.com/mongodb/mongo-ruby-driver/blob/31c59b900dc8223ab97e4019d8fafb8f197754f1/lib/mongo/connection/pool.rb#L294 Could you give me the result of sigdump? http://docs.fluentd.org/articles/trouble-shooting#dump-fluentd-internal-information I want to know...

> will the sigdump help or should I wait until the issue appears again? Yeah. If the problem happens again, sigdump result helps problem investigation.

Hmm... hard to debug because it seems the problem happens inside mongo driver, not plugin. Could you update fluent-plugin-mongo to v0.8.0? It uses mongo driver v2.x.

See: http://docs.fluentd.org/v0.12/articles/plugin-management