Repository: kafka Updated Branches: refs/heads/0.9.0 52a3e7b27 -> 653393337
MINOR: Add information to upgrade notes Credit to Gwen for some of the text. Author: Ismael Juma <[email protected]> Reviewers: Guozhang Wang <[email protected]>, Ewen Cheslack-Postava <[email protected]> Closes #678 from ijuma/mirror-maker-compatibility-note (cherry picked from commit 4ad165c0783bc49e5750292cd0e8d277e3186846) Signed-off-by: Ewen Cheslack-Postava <[email protected]> Project: http://git-wip-us.apache.org/repos/asf/kafka/repo Commit: http://git-wip-us.apache.org/repos/asf/kafka/commit/65339333 Tree: http://git-wip-us.apache.org/repos/asf/kafka/tree/65339333 Diff: http://git-wip-us.apache.org/repos/asf/kafka/diff/65339333 Branch: refs/heads/0.9.0 Commit: 6533933371d82c7c8cbaa32edca9b85b3932e1bb Parents: 52a3e7b Author: Ismael Juma <[email protected]> Authored: Tue Dec 15 20:57:05 2015 -0800 Committer: Ewen Cheslack-Postava <[email protected]> Committed: Tue Dec 15 20:58:03 2015 -0800 ---------------------------------------------------------------------- docs/upgrade.html | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/kafka/blob/65339333/docs/upgrade.html ---------------------------------------------------------------------- diff --git a/docs/upgrade.html b/docs/upgrade.html index 63348d3..c0a3078 100644 --- a/docs/upgrade.html +++ b/docs/upgrade.html @@ -19,7 +19,7 @@ <h4><a id="upgrade_9" href="#upgrade_9">Upgrading from 0.8.0, 0.8.1.X or 0.8.2.X to 0.9.0.0</a></h4> -0.9.0.0 has an inter-broker protocol change from previous versions. For a rolling upgrade: +0.9.0.0 has <a href="#upgrade_9_breaking">potential breaking changes</a> (please review before upgrading) and an inter-broker protocol change from previous versions. For a rolling upgrade: <ol> <li> Update server.properties file on all brokers and add the following property: inter.broker.protocol.version=0.8.2.X </li> <li> Upgrade the brokers. This can be done a broker at a time by simply bringing it down, updating the code, and restarting it. </li> @@ -31,13 +31,15 @@ <p><b>Note:</b> Bumping the protocol version and restarting can be done any time after the brokers were upgraded. It does not have to be immediately after. -<p><b>Note:</b> Broker IDs above 1000 are now reserved by default to automatically assigned broker IDs. If your cluster has existing broker IDs above that threshold make sure to increase the reserved.broker.max.id broker configuration property accordingly. - <h5><a id="upgrade_9_breaking" href="#upgrade_9_breaking">Potential breaking changes in 0.9.0.0</a></h5> <ul> <li> Java 1.6 is no longer supported. </li> <li> Scala 2.9 is no longer supported. </li> + <li> Broker IDs above 1000 are now reserved by default to automatically assigned broker IDs. If your cluster has existing broker IDs above that threshold make sure to increase the reserved.broker.max.id broker configuration property accordingly. </li> + <li> Configuration parameter replica.lag.max.messages was removed. Partition leaders will no longer consider the number of lagging messages when deciding which replicas are in sync. </li> + <li> Configuration parameter replica.lag.time.max.ms now refers not just to the time passed since last fetch request from replica, but also to time since the replica last caught up. Replicas that are still fetching messages from leaders but did not catch up to the latest messages in replica.lag.time.max.ms will be considered out of sync. </li> + <li> MirrorMaker no longer supports multiple target clusters. As a result it will only accept a single --consumer.config parameter. To mirror multiple source clusters, you will need at least one MirrorMaker instance per source cluster, each with its own consumer configuration. </li> <li> Tools packaged under <em>org.apache.kafka.clients.tools.*</em> have been moved to <em>org.apache.kafka.tools.*</em>. All included scripts will still function as usual, only custom code directly importing these classes will be affected. </li> <li> The default Kafka JVM performance options (KAFKA_JVM_PERFORMANCE_OPTS) have been changed in kafka-run-class.sh. </li> <li> The kafka-topics.sh script (kafka.admin.TopicCommand) now exits with non-zero exit code on failure. </li>
