mirror of https://github.com/apache/kafka.git
KAFKA-3565; Add documentation to warn user about the potential messag…
…e throughput drop due to the addition of timestamp field. Author: Jiangjie Qin <becket.qin@gmail.com> Reviewers: Ismael Juma <ismael@juma.me.uk>, Jun Rao <junrao@gmail.com> Closes #1372 from becketqin/KAFKA-3565
This commit is contained in:
parent
13130139ff
commit
7ded19a29e
|
@ -63,6 +63,13 @@ work with 0.10.0.x brokers. Therefore, 0.9.0.0 clients should be upgraded to 0.9
|
||||||
message format version. Otherwise consumers before 0.10.0.0 might break. In particular, after the message format
|
message format version. Otherwise consumers before 0.10.0.0 might break. In particular, after the message format
|
||||||
is set to 0.10.0, one should not change it back to an earlier format as it may break consumers on versions before 0.10.0.0.
|
is set to 0.10.0, one should not change it back to an earlier format as it may break consumers on versions before 0.10.0.0.
|
||||||
</p>
|
</p>
|
||||||
|
<p>
|
||||||
|
<b>Note:</b> Due to the additional timestamp introduced in each message, producers sending small messages may see a
|
||||||
|
message throughput degradation because of the increased overhead. When receiving compressed messages, 0.10.0
|
||||||
|
brokers avoid recompressing the messages, which in general reduces the latency and improves the throughput. In
|
||||||
|
certain cases, this may reduce the batching size on the producer, which could lead to worse throughput. If this
|
||||||
|
happens, users can tune linger.ms and batch.size of the producer for better throughput.
|
||||||
|
</p>
|
||||||
|
|
||||||
<h5><a id="upgrade_10_breaking" href="#upgrade_10_breaking">Potential breaking changes in 0.10.0.0</a></h5>
|
<h5><a id="upgrade_10_breaking" href="#upgrade_10_breaking">Potential breaking changes in 0.10.0.0</a></h5>
|
||||||
<ul>
|
<ul>
|
||||||
|
|
Loading…
Reference in New Issue