You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by GitBox <gi...@apache.org> on 2022/07/20 15:05:02 UTC

[GitHub] [kafka] rhauch commented on a diff in pull request #12424: RELEASE: Add 3.2 upgrade docs

rhauch commented on code in PR #12424:
URL: https://github.com/apache/kafka/pull/12424#discussion_r925721375


##########
docs/upgrade.html:
##########
@@ -61,6 +61,20 @@ <h4><a id="upgrade_3_2_0" href="#upgrade_3_2_0">Upgrading to 3.2.0 from any vers
     </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>error.tolerance</code> was fixed. When <code>error.tolerance</code>
+            was set to <code>all</code>, it was possible for offsets to not be committed and a memory leak to occur
+            (eventually resulting in an OutOfMemoryError). 

Review Comment:
   Minor suggestions:
   ```suggestion
           <li>A problem in Connect with <code>error.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. 
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: jira-unsubscribe@kafka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org