Config defaults #3299
-
Just to be sure... I noticed that the default configuration values documented for librdkafka (https://github.com/edenhill/librdkafka/blob/master/CONFIGURATION.md) are very different than the ones in the Kafka documentation (https://kafka.apache.org/documentation). For example here the default Are the defaults in the documentation of librdkafka correct? Are the Kafka defaults somehow "overridden" (batch.size is a client-side thing at the end of the day)? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
cc @edenhill |
Beta Was this translation helpful? Give feedback.
-
While we try to maintain the same default behaviour as the Java clients, there are some instances where we can't (because of historical (librdkafka predates the Java clients and has a strict backwards compatible modus) or implementation reasons) or won't (because we disagree). Our defaults are balanced between latency and throughput and should work well for the majority of applications, and it is generally not recommended to tweak things like batch sizes and timeouts unless really necessary. The properties that are marked with high importance are the ones an application developer should consider. |
Beta Was this translation helpful? Give feedback.
While we try to maintain the same default behaviour as the Java clients, there are some instances where we can't (because of historical (librdkafka predates the Java clients and has a strict backwards compatible modus) or implementation reasons) or won't (because we disagree).
Our defaults are balanced between latency and throughput and should work well for the majority of applications, and it is generally not recommended to tweak things like batch sizes and timeouts unless really necessary.
The properties that are marked with high importance are the ones an application developer should consider.