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-3164: Document client and mirrormaker upgrade procedure/require…
Date Sun, 31 Jan 2016 00:23:59 GMT
Repository: kafka
Updated Branches:
  refs/heads/0.9.0 220d49849 -> d1ff6c75f


KAFKA-3164: Document client and mirrormaker upgrade procedure/require…

…ments

Author: Grant Henke <granthenke@gmail.com>

Reviewers: Gwen Shapira

Closes #838 from granthenke/upgrade-docs


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

Branch: refs/heads/0.9.0
Commit: d1ff6c75f261e4ca2e0c87e4c719fb8279765654
Parents: 220d498
Author: Grant Henke <granthenke@gmail.com>
Authored: Sat Jan 30 16:22:42 2016 -0800
Committer: Gwen Shapira <cshapi@gmail.com>
Committed: Sat Jan 30 16:23:50 2016 -0800

----------------------------------------------------------------------
 docs/upgrade.html | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/kafka/blob/d1ff6c75/docs/upgrade.html
----------------------------------------------------------------------
diff --git a/docs/upgrade.html b/docs/upgrade.html
index 50fc119..96d1a29 100644
--- a/docs/upgrade.html
+++ b/docs/upgrade.html
@@ -19,7 +19,10 @@
 
 <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 <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:
+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. 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.
+
+<p><b>For a rolling upgrade:</b></p>
+
 <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>


Mime
View raw message