This is an automated email from the ASF dual-hosted git repository. mjsax pushed a commit to branch 3.4 in repository https://gitbox.apache.org/repos/asf/kafka.git
commit f528262d412dad578c7f2c90d464a5f47f16e89e Author: Luke Chen <show...@gmail.com> AuthorDate: Thu Dec 29 07:02:21 2022 +0800 KAFKA-13439: move upgrade note to stream upgrade doc (#12008) Reviewers: Matthias J. Sax <matth...@confluent.io> --- docs/streams/upgrade-guide.html | 12 ++++++++++++ docs/upgrade.html | 10 ---------- 2 files changed, 12 insertions(+), 10 deletions(-) diff --git a/docs/streams/upgrade-guide.html b/docs/streams/upgrade-guide.html index bba7068bef7..39be48975e4 100644 --- a/docs/streams/upgrade-guide.html +++ b/docs/streams/upgrade-guide.html @@ -51,6 +51,18 @@ <li> update your code and swap old code and jar file with new code and new jar file </li> <li> restart all new ({{fullDotVersion}}) application instances </li> </ul> + <p> + Note: The cooperative rebalancing protocol has been the default since 2.4, but we have continued to support the + eager rebalancing protocol to provide users an upgrade path. This support will be dropped in a future release, + so any users still on the eager protocol should prepare to finish upgrading their applications to the cooperative protocol in version 3.1. + This only affects users who are still on a version older than 2.4, and users who have upgraded already but have not yet + removed the <code>upgrade.from</code> config that they set when upgrading from a version below 2.4. + Users fitting into the latter case will simply need to unset this config when upgrading beyond 3.1, + while users in the former case will need to follow a slightly different upgrade path if they attempt to upgrade from 2.3 or below to a version above 3.1. + Those applications will need to go through a bridge release, by first upgrading to a version between 2.4 - 3.1 and setting the <code>upgrade.from</code> config, + then removing that config and upgrading to the final version above 3.1. See <a href="https://issues.apache.org/jira/browse/KAFKA-8575">KAFKA-8575</a> + for more details. + </p> <h3 class="anchor-heading"><a id="streams_notable_changes" class="anchor-link"></a><a href="#streams_notable_changes">Notable compatibility changes in past releases</a></h3> <p> diff --git a/docs/upgrade.html b/docs/upgrade.html index d96cddbdbcb..1ea6be319e3 100644 --- a/docs/upgrade.html +++ b/docs/upgrade.html @@ -238,16 +238,6 @@ and <code>iotime-total</code>. Please use <code>bufferpool-wait-time-ns-total</code>, <code>io-wait-time-ns-total</code>, and <code>io-time-ns-total</code> instead. See <a href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-773%3A+Differentiate+consistently+metric+latency+measured+in+millis+and+nanos">KIP-773</a> for more details.</li> - <li>The cooperative rebalancing protocol has been the default since 2.4, but we have continued to support the - eager rebalancing protocol to provide users an upgrade path. This support will be dropped in a future release, - so any users still on the eager protocol should prepare to finish upgrading their applications to the cooperative protocol in version 3.1. - This only affects users who are still on a version older than 2.4, and users who have upgraded already but have not yet - removed the <code>upgrade.from</code> config that they set when upgrading from a version below 2.4. - Users fitting into the latter case will simply need to unset this config when upgrading beyond 3.1, - while users in the former case will need to follow a slightly different upgrade path if they attempt to upgrade from 2.3 or below to a version above 3.1. - Those applications will need to go through a bridge release, by first upgrading to a version between 2.4 - 3.1 and setting the <code>upgrade.from</code> config, - then removing that config and upgrading to the final version above 3.1. See <a href="https://issues.apache.org/jira/browse/KAFKA-8575">KAFKA-8575</a> - for more details.</li> <li>IBP 3.1 introduces topic IDs to FetchRequest as a part of <a href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-516%3A+Topic+Identifiers">KIP-516</a>.</li> </ul>