kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From maniku...@apache.org
Subject [kafka] branch 2.4 updated: MINOR: Add upgrade docs for 2.4.0 release
Date Tue, 22 Oct 2019 15:22:04 GMT
This is an automated email from the ASF dual-hosted git repository.

manikumar pushed a commit to branch 2.4
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/2.4 by this push:
     new cecb1e2  MINOR: Add upgrade docs for 2.4.0 release
cecb1e2 is described below

commit cecb1e2fa583d40fb42231a730df6fce1e7d19c3
Author: Manikumar Reddy <manikumar.reddy@gmail.com>
AuthorDate: Tue Oct 22 20:51:10 2019 +0530

    MINOR: Add upgrade docs for 2.4.0 release
    
    Author: Manikumar Reddy <manikumar.reddy@gmail.com>
    
    Reviewers: Reviewers: Manikumar Reddy <manikumar.reddy@gmail.com>
    
    Closes #7530 from omkreddy/2.4-upgrade-docs
    
    (cherry picked from commit f46eb292f5be892fbfcd6551d57c5a425c514673)
    Signed-off-by: Manikumar Reddy <manikumar@confluent.io>
---
 docs/upgrade.html | 42 ++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 42 insertions(+)

diff --git a/docs/upgrade.html b/docs/upgrade.html
index 6d9f702..65c7ba9 100644
--- a/docs/upgrade.html
+++ b/docs/upgrade.html
@@ -19,6 +19,48 @@
 
 <script id="upgrade-template" type="text/x-handlebars-template">
 
+<h4><a id="upgrade_2_4_0" href="#upgrade_2_4_0">Upgrading from 0.8.x, 0.9.x,
0.10.0.x, 0.10.1.x, 0.10.2.x, 0.11.0.x, 1.0.x, 1.1.x, 2.0.x or 2.1.x or 2.2.x or 2.3.x to
2.4.0</a></h4>
+
+<p><b>If you are upgrading from a version prior to 2.1.x, please see the note
below about the change to the schema used to store consumer offsets.
+    Once you have changed the inter.broker.protocol.version to the latest version, it will
not be possible to downgrade to a version prior to 2.1.</b></p>
+
+<p><b>For a rolling upgrade:</b></p>
+
+<ol>
+    <li> Update server.properties on all brokers and add the following properties.
CURRENT_KAFKA_VERSION refers to the version you
+        are upgrading from. CURRENT_MESSAGE_FORMAT_VERSION refers to the message format version
currently in use. If you have previously
+        overridden the message format version, you should keep its current value. Alternatively,
if you are upgrading from a version prior
+        to 0.11.0.x, then CURRENT_MESSAGE_FORMAT_VERSION should be set to match CURRENT_KAFKA_VERSION.
+        <ul>
+            <li>inter.broker.protocol.version=CURRENT_KAFKA_VERSION (e.g. 0.10.0, 0.11.0,
1.0, 2.0, 2.2).</li>
+            <li>log.message.format.version=CURRENT_MESSAGE_FORMAT_VERSION  (See <a
href="#upgrade_10_performance_impact">potential performance impact
+                following the upgrade</a> for the details on what this configuration
does.)</li>
+        </ul>
+        If you are upgrading from version 0.11.0.x or above, and you have not overridden
the message format, then you only need to override
+        the inter-broker protocol version.
+        <ul>
+            <li>inter.broker.protocol.version=CURRENT_KAFKA_VERSION (0.11.0, 1.0, 1.1,
2.0, 2.1, 2.2, 2.3).</li>
+        </ul>
+    </li>
+    <li> Upgrade the brokers one at a time: shut down the broker, update the code,
and restart it. Once you have done so, the
+        brokers will be running the latest version and you can verify that the cluster's
behavior and performance meets expectations.
+        It is still possible to downgrade at this point if there are any problems.
+    </li>
+    <li> Once the cluster's behavior and performance has been verified, bump the protocol
version by editing
+        <code>inter.broker.protocol.version</code> and setting it to 2.4.
+    </li>
+    <li> Restart the brokers one by one for the new protocol version to take effect.
Once the brokers begin using the latest
+        protocol version, it will no longer be possible to downgrade the cluster to an older
version.
+    </li>
+    <li> If you have overridden the message format version as instructed above, then
you need to do one more rolling restart to
+        upgrade it to its latest version. Once all (or most) consumers have been upgraded
to 0.11.0 or later,
+        change log.message.format.version to 2.4 on each broker and restart them one by one.
Note that the older Scala clients,
+        which are no longer maintained, do not support the message format introduced in 0.11,
so to avoid conversion costs
+        (or to take advantage of <a href="#upgrade_11_exactly_once_semantics">exactly
once semantics</a>),
+        the newer Java clients must be used.
+    </li>
+</ol>
+
 <h5><a id="upgrade_240_notable" href="#upgrade_240_notable">Notable changes in
2.4.0</a></h5>
 <ul>
     <li>A new Admin API has been added for partition reassignments. Due to changing
the way Kafka propagates reassignment information,


Mime
View raw message