kafka
Last updated
Was this helpful?
Last updated
Was this helpful?
The out_kafka Output plugin writes records into . This document doesn't describe all parameters. If you want to know full features, check the Further Reading section.
out_kafka is included in td-agent2 after v2.3.3. Fluentd gem users will need to install the fluent-plugin-kafka gem using the following command.
Please make sure that you have enough space in the buffer_path directory. Running out of disk space is a problem frequently reported by users.
The value must be kafka_buffered.
The list of all seed brokers, with their host and port information.
The name of default topic (default: nil).
The name of default partition key (default: nil).
The name of default message key (default: nil).
The format of each message. The available options are json, ltsv, msgpack, attr:<record name>, <formatter name>. msgpack is recommended since it's more compact and faster.
The number of times to retry sending of messages to a leader (default: 1).
The number of acks required per request (default: -1).
How long the producer waits for acks. The unit is seconds (default: nil => Use default of ruby-kafka library)
The codec the producer uses to compress messages (default: nil). The available options are gzip and snappy. When you use snappy, you need to install snappy gem by td-agent-gem command.
For advanced usage, you can tune Fluentd's internal buffering mechanism with these parameters.
The interval between data flushes. The default is 60s. The suffixes "s" (seconds), "m" (minutes), and "h" (hours) can be used.
If set to true, Fluentd waits for the buffer to flush at shutdown. By default, it is set to true for Memory Buffer and false for File Buffer.
The initial and maximum intervals between write retries. The default values are 1.0 seconds and unset (no limit). The interval doubles (with +/-12.5% randomness) every retry until max_retry_wait is reached.
Since td-agent will retry 17 times before giving up by default (see the retry_limit parameter for details), the sleep interval can be up to approximately 131072 seconds (roughly 36 hours) in the default configurations.
The limit on the number of retries before buffered data is discarded, and an option to disable that limit (if true, the value of retry_limit is ignored and there is no limit). The default values are 17 and false (not disabled). If the limit is reached, buffered data is discarded and the retry interval is reset to its initial value (retry_wait).
The number of threads to flush the buffer. This option can be used to parallelize writes into the output(s) designated by the output plugin. Increasing the number of threads improves the flush throughput to hide write / network latency. The default is 1.
The threshold for checking chunk flush performance. The default value is 20.0 seconds. Note that parameter type is float, not time.
If chunk flush takes longer time than this threshold, fluentd logs warning message like below:
The log_level option allows the user to set different levels of logging for each plugin. The supported log levels are: fatal, error, warn, info, debug, and trace.
This page doesn't describe all the possible configurations. If you want to know about other configurations, please check the link below.
Please see the article for the basic structure and syntax of the configuration file.
The buffer type is memory by default () for the ease of testing, however file () buffer type is always recommended for the production deployments. If you use file buffer type, buffer_path parameter is required.
The length of the chunk queue and the size of each chunk, respectively. Please see the article for the basic buffer structure. The default values are 64 and 8m, respectively. The suffixes "k" (KB), "m" (MB), and "g" (GB) can be used for buffer_chunk_limit.
Please see the for further details.
If this article is incorrect or outdated, or omits critical information, please . is a open source project under . All components are available under the Apache 2 License.
