kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jun...@apache.org
Subject kafka git commit: KAFKA-3565; Add documentation to warn user about the potential messag…
Date Sun, 15 May 2016 16:04:19 GMT
Repository: kafka
Updated Branches:
  refs/heads/trunk 13130139f -> 7ded19a29


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


Project: http://git-wip-us.apache.org/repos/asf/kafka/repo
Commit: http://git-wip-us.apache.org/repos/asf/kafka/commit/7ded19a2
Tree: http://git-wip-us.apache.org/repos/asf/kafka/tree/7ded19a2
Diff: http://git-wip-us.apache.org/repos/asf/kafka/diff/7ded19a2

Branch: refs/heads/trunk
Commit: 7ded19a29ec140de93d57a9eb01722e6a8f2012a
Parents: 1313013
Author: Jiangjie Qin <becket.qin@gmail.com>
Authored: Sun May 15 09:04:21 2016 -0700
Committer: Jun Rao <junrao@gmail.com>
Committed: Sun May 15 09:04:21 2016 -0700

----------------------------------------------------------------------
 docs/upgrade.html | 7 +++++++
 1 file changed, 7 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/kafka/blob/7ded19a2/docs/upgrade.html
----------------------------------------------------------------------
diff --git a/docs/upgrade.html b/docs/upgrade.html
index a6754bc..c5431aa 100644
--- a/docs/upgrade.html
+++ b/docs/upgrade.html
@@ -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
     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>
+    <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>
 <ul>


Mime
View raw message