kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gwens...@apache.org
Subject kafka git commit: KAFKA-3463: change default receive buffer size for consumer to 64K
Date Fri, 25 Mar 2016 19:51:59 GMT
Repository: kafka
Updated Branches:
  refs/heads/trunk d3a66a653 -> d691faf98

KAFKA-3463: change default receive buffer size for consumer to 64K

Author: Jason Gustafson <jason@confluent.io>

Reviewers: Gwen Shapira

Closes #1140 from hachikuji/KAFKA-3463

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

Branch: refs/heads/trunk
Commit: d691faf98cb573c4e92748d95d5c8afc492db806
Parents: d3a66a6
Author: Jason Gustafson <jason@confluent.io>
Authored: Fri Mar 25 12:51:54 2016 -0700
Committer: Gwen Shapira <cshapi@gmail.com>
Committed: Fri Mar 25 12:51:54 2016 -0700

 .../org/apache/kafka/clients/consumer/ConsumerConfig.java    | 2 +-
 docs/upgrade.html                                            | 8 +++++++-
 2 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/clients/src/main/java/org/apache/kafka/clients/consumer/ConsumerConfig.java b/clients/src/main/java/org/apache/kafka/clients/consumer/ConsumerConfig.java
index c97c8fb..69c4a36 100644
--- a/clients/src/main/java/org/apache/kafka/clients/consumer/ConsumerConfig.java
+++ b/clients/src/main/java/org/apache/kafka/clients/consumer/ConsumerConfig.java
@@ -243,7 +243,7 @@ public class ConsumerConfig extends AbstractConfig {
-                                        32 * 1024,
+                                        64 * 1024,

diff --git a/docs/upgrade.html b/docs/upgrade.html
index f1e1e40..060c3de 100644
--- a/docs/upgrade.html
+++ b/docs/upgrade.html
@@ -64,7 +64,7 @@ work with 0.10.0.x brokers. Therefore, clients should be upgraded
to 0.9
     is set to 0.10.0, one should not change it back to an earlier format as it may break
consumers on versions before
-<h5><a id="upgrade_10_breaking" href="#upgrade_10_breaking">potential breaking
changes in</a></h5>
+<h5><a id="upgrade_10_breaking" href="#upgrade_10_breaking">Potential breaking
changes in</a></h5>
     <li> Starting from Kafka, the message format version in Kafka is represented
as the Kafka version. For example, message format 0.9.0 refers to the highest message version
supported by Kafka 0.9.0. </li>
     <li> Message format 0.10.0 has been introduced and it is used by default. It includes
a timestamp field in the messages and relative offsets are used for compressed messages. </li>
@@ -81,6 +81,12 @@ work with 0.10.0.x brokers. Therefore, clients should be upgraded
to 0.9
     <li> The 0.7 KafkaMigrationTool is no longer packaged with Kafka. If you need to
migrate from 0.7 to 0.10.0, please migrate to 0.8 first and then follow the documented upgrade
process to upgrade from 0.8 to 0.10.0. </li>
+<h5><a id="upgrade_10_notable" href="#upgrade_10_notable">Notable changes in</a></h5>
+    <li> The default value of the configuration parameter <code>receive.buffer.bytes</code>
is now 64K for the new consumer </li>
 <h4><a id="upgrade_9" href="#upgrade_9">Upgrading from 0.8.0, 0.8.1.X or 0.8.2.X
to</a></h4> has <a href="#upgrade_9_breaking">potential breaking changes</a> (please
review before upgrading) and an inter-broker protocol change from previous versions. This
means that upgraded brokers and clients may not be compatible with older versions. It is important
that you upgrade your Kafka cluster before upgrading your clients. If you are using MirrorMaker
downstream clusters should be upgraded first as well.

View raw message