[SPARK-39848][BUILD] Upgrade Kafka to 3.2.1 #37261
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR aims to upgrade Apache Kafka to 3.2.1.
Why are the changes needed?
Apache Kafka 3.2.1 is released.
Apache Kafka 3.2.1 has the following patches.
KAFKA-14013 Limit the length of the
reasonfield sent on the wire BugKAFKA-13474 Regression in dynamic update of broker certificate
KAFKA-13572 Negative value for 'Preferred Replica Imbalance' metric
KAFKA-13773 Data loss after recovery from crash due to full hard disk
KAFKA-13861 validateOnly request field does not work for CreatePartition requests in Kraft mode.
KAFKA-13899 Inconsistent error codes returned from AlterConfig APIs
KAFKA-13998 JoinGroupRequestData 'reason' can be too large
KAFKA-14010 alterISR request won't retry when receiving retriable error
KAFKA-14024 Consumer stuck during cooperative rebalance for Commit offset in onJoinPrepare
KAFKA-14035 QuorumController handleRenounce throws NPE
KAFKA-14055 Transaction markers may be lost during cleaning if data keys conflict with marker keys
KAFKA-14062 OAuth client token refresh fails with SASL extensions
KAFKA-14079 Source task will not commit offsets and develops memory leak if "error.tolerance" is set to "all"
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs