This is an automated email from the ASF dual-hosted git repository.
stanislavkozlovski pushed a commit to branch 3.6
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/3.6 by this push:
new e38a1ed757f MINOR: Reconcile upgrade.html with kafka-site/36's version
(#15406)
e38a1ed757f is described below
commit e38a1ed757f4347cc6a40c36e36bb9b64264c196
Author: Stanislav Kozlovski <stanislav_kozlov...@outlook.com>
AuthorDate: Thu Feb 22 10:39:58 2024 +0100
MINOR: Reconcile upgrade.html with kafka-site/36's version (#15406)
The usual flow of updating the upgrade.html docs is to first do it in
apache/kafka/trunk, then cherry-pick to the relative release branch and then
copy into the kafka-site repo.
It seems like this was not done with a few commits updating the 3.6.1,
3.5.2 and 3.5.1, resulting in kafka-site's latest upgrade.html containing
content that isn't here. This was caught while we were adding the 3.7 upgrade
docs.
This patch reconciles both files by taking the extra changes from
kafka-site and placing them here. This was done by simply comparing a diff of
both changes and taking the ones that apply
---
docs/upgrade.html | 40 +++++++++++++++++++++++++++++++++++++---
1 file changed, 37 insertions(+), 3 deletions(-)
diff --git a/docs/upgrade.html b/docs/upgrade.html
index 4bab0545b87..e9a985076be 100644
--- a/docs/upgrade.html
+++ b/docs/upgrade.html
@@ -19,9 +19,10 @@
<script id="upgrade-template" type="text/x-handlebars-template">
-<h4><a id="upgrade_3_6_0" href="#upgrade_3_6_0">Upgrading to 3.6.0 from any
version 0.8.x through 3.5.x</a></h4>
- <h5><a id="upgrade_360_zk" href="#upgrade_360_zk">Upgrading
ZooKeeper-based clusters</a></h5>
+<h4><a id="upgrade_3_6_1" href="#upgrade_3_6_1">Upgrading to 3.6.1 from any
version 0.8.x through 3.5.x</a></h4>
+
+ <h5><a id="upgrade_361_zk" href="#upgrade_361_zk">Upgrading
ZooKeeper-based clusters</a></h5>
<p><b>If you are upgrading from a version prior to 2.1.x, please see the
note in step 5 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>
@@ -62,7 +63,7 @@
</li>
</ol>
- <h5><a id="upgrade_360_kraft" href="#upgrade_360_kraft">Upgrading
KRaft-based clusters</a></h5>
+ <h5><a id="upgrade_361_kraft" href="#upgrade_361_kraft">Upgrading
KRaft-based clusters</a></h5>
<p><b>If you are upgrading from a version prior to 3.3.0, please see the
note in step 3 below. Once you have changed the metadata.version to the latest
version, it will not be possible to downgrade to a version prior to
3.3-IV0.</b></p>
<p><b>For a rolling upgrade:</b></p>
@@ -123,6 +124,39 @@
</li>
</ul>
+<h4><a id="upgrade_3_5_2" href="#upgrade_3_5_2">Upgrading to 3.5.2 from any
version 0.8.x through 3.4.x</a></h4>
+ All upgrade steps remain same as <a href="#upgrade_3_5_0">upgrading to
3.5.0</a>
+ <h5><a id="upgrade_352_notable" href="#upgrade_352_notable">Notable
changes in 3.5.2</a></h5>
+ <ul>
+ <li>
+ When migrating producer ID blocks from ZK to KRaft, there could be
duplicate producer IDs being given to
+ transactional or idempotent producers. This can cause long term
problems since the producer IDs are
+ persisted and reused for a long time.
+ See <a
href="https://issues.apache.org/jira/browse/KAFKA-15552";>KAFKA-15552</a> for
more details.
+ </li>
+ <li>
+ In 3.5.0 and 3.5.1, there could be an issue that the empty ISR is
returned from controller after AlterPartition request
+ during rolling upgrade. This issue will impact the availability of the
topic partition.
+ See <a
href="https://issues.apache.org/jira/browse/KAFKA-15353";>KAFKA-15353</a> for
more details.
+ </li>
+</ul>
+
+<h4><a id="upgrade_3_5_1" href="#upgrade_3_5_1">Upgrading to 3.5.1 from any
version 0.8.x through 3.4.x</a></h4>
+ All upgrade steps remain same as <a href="#upgrade_3_5_0">upgrading to
3.5.0</a>
+ <h5><a id="upgrade_351_notable" href="#upgrade_351_notable">Notable
changes in 3.5.1</a></h5>
+ <ul>
+ <li>
+ Upgraded the dependency, snappy-java, to a version which is not
vulnerable to
+ <a
href="https://nvd.nist.gov/vuln/detail/CVE-2023-34455";>CVE-2023-34455.</a>
+ You can find more information about the CVE at <a
href="https://kafka.apache.org/cve-list#CVE-2023-34455";>Kafka CVE list.</a>
+ </li>
+ <li>
+ Fixed a regression introduced in 3.3.0, which caused
<code>security.protocol</code> configuration values to be restricted to
+ upper case only. After the fix, <code>security.protocol</code> values
are case insensitive.
+ See <a
href="https://issues.apache.org/jira/browse/KAFKA-15053";>KAFKA-15053</a> for
details.
+ </li>
+</ul>
+
<h4><a id="upgrade_3_5_0" href="#upgrade_3_5_0">Upgrading to 3.5.0 from any
version 0.8.x through 3.4.x</a></h4>
<h5><a id="upgrade_350_zk" href="#upgrade_350_zk">Upgrading
ZooKeeper-based clusters</a></h5>
