This is an automated email from the ASF dual-hosted git repository.
davidarthur pushed a commit to branch 3.2
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/3.2 by this push:
new cb14b100ad Add 3.2.1 upgrade docs (#12424)
cb14b100ad is described below
commit cb14b100ad6830d573819c13c44c91ecd1653c9b
Author: David Arthur <[email protected]>
AuthorDate: Wed Jul 20 15:26:26 2022 -0400
Add 3.2.1 upgrade docs (#12424)
Reviewers: Randall Hauch <[email protected]>, Guozhang Wang
<[email protected]>
---
docs/upgrade.html | 18 +++++++++++++++++-
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/docs/upgrade.html b/docs/upgrade.html
index f7d9bfcf36..b0a823a1ea 100644
--- a/docs/upgrade.html
+++ b/docs/upgrade.html
@@ -19,7 +19,7 @@
<script id="upgrade-template" type="text/x-handlebars-template">
-<h4><a id="upgrade_3_2_0" href="#upgrade_3_2_0">Upgrading to 3.2.0 from any
version 0.8.x through 3.1.x</a></h4>
+<h4><a id="upgrade_3_2_1" href="#upgrade_3_2_1">Upgrading to 3.2.1 from any
version 0.8.x through 3.1.x</a></h4>
<p><b>If you are upgrading from a version prior to 2.1.x, please see the note
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>
@@ -61,6 +61,22 @@
</li>
</ol>
+<h5><a id="upgrade_321_notable" href="#upgrade_321_notable">Notable changes in
3.2.1</a></h5>
+ <ul>
+ <li>A problem with OAuth token refresh was fixed. During token
refresh, the Kafka client was not including
+ the SASL extensions which were present during the initial
authentication. This leads to authentication
+ failures. See <a
href="https://issues.apache.org/jira/browse/KAFKA-14062";>KAFKA-14062</a> for
details.</li>
+ <li>A problem in Connect with <code>errors.tolerance</code> was fixed.
Starting in 3.2.0, when
+ a source connector uses <code>errors.tolerance=all</code> and
Connect's producer fails to
+ successfully send a source record to the topic, the error is
properly reported and the connector
+ continues, but Connect stops committing source offsets for that
source connector and a
+ memory leak will eventually cause the Connect worker to fail with
an OutOfMemoryError.
+ See <a
href="https://issues.apache.org/jira/browse/KAFKA-14079";>KAFKA-14079</a> for
details.</li>
+ <li>A regression in the cooperative rebalance was fixed. Changes
introduced in 3.2.0 to the offset commit
+ behavior prior to rebalancing could lead to the consumer getting
stuck. See
+ <a
href="https://issues.apache.org/jira/browse/KAFKA-14024";>KAFKA-14024</a> for
details.</li>
+ </ul>
+
<h5><a id="upgrade_320_notable" href="#upgrade_320_notable">Notable changes in
3.2.0</a></h5>
<ul>
<li>Idempotence for the producer is enabled by default if no
conflicting configurations are set. In 3.0.0 and 3.1.0, a bug prevented this
default from being applied,
