kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject kafka git commit: MINOR: Add upgrade notes for KIP-62
Date Tue, 04 Oct 2016 04:17:44 GMT
Repository: kafka
Updated Branches:
  refs/heads/0.10.1 3d7e3d685 -> aafc86928

MINOR: Add upgrade notes for KIP-62

Author: Jason Gustafson <jason@confluent.io>

Reviewers: Guozhang Wang <wangguoz@gmail.com>

Closes #1956 from hachikuji/add-kip-62-upgrade-notes

(cherry picked from commit 1a396c9cf22441a7afa8ec9c4a94a48f881cdd90)
Signed-off-by: Jason Gustafson <jason@confluent.io>

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

Branch: refs/heads/0.10.1
Commit: aafc869286473ca480e5529a8c1ae86284976503
Parents: 3d7e3d6
Author: Jason Gustafson <jason@confluent.io>
Authored: Mon Oct 3 21:17:11 2016 -0700
Committer: Jason Gustafson <jason@confluent.io>
Committed: Mon Oct 3 21:17:48 2016 -0700

 docs/upgrade.html | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/upgrade.html b/docs/upgrade.html
index 4f9d4f2..4f23a95 100644
--- a/docs/upgrade.html
+++ b/docs/upgrade.html
@@ -64,6 +64,7 @@ Note: Because new protocols are introduced, it is important to upgrade your
     <li> Kafka clusters can now be uniquely identified by a cluster id. It will be
automatically generated when a broker is upgraded to The cluster id is available
via the kafka.server:type=KafkaServer,name=ClusterId metric and it is part of the Metadata
response. Serializers, client interceptors and metric reporters can receive the cluster id
by implementing the ClusterResourceListener interface. </li>
     <li> The BrokerState "RunningAsController" (value 4) has been removed. Due to a
bug, a broker would only be in this state briefly before transitioning out of it and hence
the impact of the removal should be minimal. The recommended way to detect if a given broker
is the controller is via the kafka.controller:type=KafkaController,name=ActiveControllerCount
metric. </li>
     <li> The new Java Consumer now allows users to search offsets by timestamp on partitions.
+    <li> The new Java Consumer now supports heartbeating from a background thread.
There is a new configuration <code>max.poll.interval.ms</code> which controls
the maximum time between poll invocations before the consumer will proactively leave the group
(5 minutes by default). The default value of <code>session.timeout.ms</code> has
been adjusted down to 10 seconds, and the default value of <code>max.poll.records</code>
has been changed to 500.</li>
     <li> When using an Authorizer and a user doesn't have <b>Describe</b>
authorization on a topic, the broker will no
          longer return TOPIC_AUTHORIZATION_FAILED errors to requests since this leaks topic
          error code will be returned. This may cause unexpected timeouts or delays when using
the producer and consumer since

View raw message