Repository: kafka Updated Branches: refs/heads/trunk 2c9796114 -> b9f1c6032
MINOR: Mention `log.message.format.version=0.10.0` in rolling upgrade section We had mentioned this step in the performance impact section in the middle of a long paragraph, which made it easy to miss. I also tweaked the reason for setting `log.message.format.version` as it could be misinterpreted previously. Author: Ismael Juma <[email protected]> Reviewers: Ewen Cheslack-Postava <[email protected]> Closes #1514 from ijuma/tweak-upgrade-notes Project: http://git-wip-us.apache.org/repos/asf/kafka/repo Commit: http://git-wip-us.apache.org/repos/asf/kafka/commit/b9f1c603 Tree: http://git-wip-us.apache.org/repos/asf/kafka/tree/b9f1c603 Diff: http://git-wip-us.apache.org/repos/asf/kafka/diff/b9f1c603 Branch: refs/heads/trunk Commit: b9f1c60328da8a494424e30e7ebcb75d31c6fe85 Parents: 2c97961 Author: Ismael Juma <[email protected]> Authored: Sun Jun 19 16:03:40 2016 -0700 Committer: Ewen Cheslack-Postava <[email protected]> Committed: Sun Jun 19 16:03:40 2016 -0700 ---------------------------------------------------------------------- docs/upgrade.html | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/kafka/blob/b9f1c603/docs/upgrade.html ---------------------------------------------------------------------- diff --git a/docs/upgrade.html b/docs/upgrade.html index dec0808..a9a1443 100644 --- a/docs/upgrade.html +++ b/docs/upgrade.html @@ -31,12 +31,15 @@ work with 0.10.0.x brokers. Therefore, 0.9.0.0 clients should be upgraded to 0.9 <ol> <li> Update server.properties file on all brokers and add the following property: inter.broker.protocol.version=CURRENT_KAFKA_VERSION (e.g. 0.8.2 or 0.9.0.0). - We recommend that users set log.message.format.version=CURRENT_KAFKA_VERSION as well to avoid a performance regression - during upgrade. See <a href="#upgrade_10_performance_impact">potential performance impact during upgrade</a> for the details. + We recommend that users set log.message.format.version=CURRENT_KAFKA_VERSION as well to ensure that performance of 0.8 and 0.9 consumers is not affected + during the upgrade. See <a href="#upgrade_10_performance_impact">potential performance impact during upgrade</a> for the details. </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> <li> Once the entire cluster is upgraded, bump the protocol version by editing inter.broker.protocol.version and setting it to 0.10.0.0. </li> <li> Restart the brokers one by one for the new protocol version to take effect. </li> + <li> Once most consumers have been upgraded to 0.10.0 and if you followed the recommendation to set log.message.format.version=CURRENT_KAFKA_VERSION, change + log.message.format.version to 0.10.0 on each broker and restart them one by one. + </li> </ol> <p><b>Note:</b> If you are willing to accept downtime, you can simply take all the brokers down, update the code and start all of them. They will start with the new protocol by default.
