Repository: kafka-site Updated Branches: refs/heads/asf-site 606a0afdf -> 2fb544c1e
Sync KAFKA-6238 which fixes message format upgrade instructions Project: http://git-wip-us.apache.org/repos/asf/kafka-site/repo Commit: http://git-wip-us.apache.org/repos/asf/kafka-site/commit/2fb544c1 Tree: http://git-wip-us.apache.org/repos/asf/kafka-site/tree/2fb544c1 Diff: http://git-wip-us.apache.org/repos/asf/kafka-site/diff/2fb544c1 Branch: refs/heads/asf-site Commit: 2fb544c1e550b7a2cc12292900a58254bd414f06 Parents: 606a0af Author: Jason Gustafson <ja...@confluent.io> Authored: Sun Nov 26 09:32:21 2017 -0800 Committer: Jason Gustafson <ja...@confluent.io> Committed: Sun Nov 26 09:32:21 2017 -0800 ---------------------------------------------------------------------- 10/upgrade.html | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/kafka-site/blob/2fb544c1/10/upgrade.html ---------------------------------------------------------------------- diff --git a/10/upgrade.html b/10/upgrade.html index eed0bc4..27c7081 100644 --- a/10/upgrade.html +++ b/10/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>
