You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kafka.apache.org by ij...@apache.org on 2017/11/23 14:46:34 UTC

kafka git commit: KAFKA-6238; Fix 1.0.0 upgrade instructions relating to the message format version

Repository: kafka
Updated Branches:
  refs/heads/trunk 90da94c38 -> 062c5568e


KAFKA-6238; Fix 1.0.0 upgrade instructions relating to the message format version

The upgrade instructions concerning the message format versions did not account
for upgrades from versions prior to 0.11.0.x.

Author: Jason Gustafson <ja...@confluent.io>

Reviewers: Ismael Juma <is...@juma.me.uk>

Closes #4256 from hachikuji/KAFKA-6328


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

Branch: refs/heads/trunk
Commit: 062c5568e13ecde4585dae8aeb38ff103632111e
Parents: 90da94c
Author: Jason Gustafson <ja...@confluent.io>
Authored: Thu Nov 23 14:46:09 2017 +0000
Committer: Ismael Juma <is...@juma.me.uk>
Committed: Thu Nov 23 14:46:21 2017 +0000

----------------------------------------------------------------------
 docs/upgrade.html | 17 +++++++++++++++--
 1 file changed, 15 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/kafka/blob/062c5568/docs/upgrade.html
----------------------------------------------------------------------
diff --git a/docs/upgrade.html b/docs/upgrade.html
index eed0bc4..27c7081 100644
--- a/docs/upgrade.html
+++ b/docs/upgrade.html
@@ -28,8 +28,16 @@
 
 <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 current message format version currently in use. If you have
-        not overridden the message format previously, then CURRENT_MESSAGE_FORMAT_VERSION should be set to match CURRENT_KAFKA_VERSION.
+        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.8.2, 0.9.0, 0.10.0, 0.10.1, 0.10.2, 0.11.0).</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 0.11.0.x and you have not overridden the message format, then you only need to override
+	the inter-broker protocol format.
         <ul>
             <li>inter.broker.protocol.version=CURRENT_KAFKA_VERSION (e.g. 0.8.2, 0.9.0, 0.10.0, 0.10.1, 0.10.2, 0.11.0).</li>
         </ul>
@@ -37,6 +45,11 @@
     <li> Upgrade the brokers one at a time: shut down the broker, update the code, and restart it. </li>
     <li> Once the entire cluster is upgraded, bump the protocol version by editing <code>inter.broker.protocol.version</code> and setting it to 1.0.
     <li> Restart the brokers one by one for the new protocol version to take effect. </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 1.0 on each broker and restart them one by one. Note that the older Scala consumer 
+        does not support the new message format introduced in 0.11, so to avoid the performance cost of down-conversion (or to
+        take advantage of <a href="#upgrade_11_exactly_once_semantics">exactly once semantics</a>), the newer Java consumer must be used.</li>
 </ol>
 
 <p><b>Additional Upgrade Notes:</b></p>