You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kafka.apache.org by mj...@apache.org on 2026/06/09 23:15:37 UTC
(kafka) branch 4.3 updated: MINOR: update AK/KS doc to (#22525)
This is an automated email from the ASF dual-hosted git repository.
mjsax pushed a commit to branch 4.3
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/4.3 by this push:
new b1b779f2476 MINOR: update AK/KS doc to (#22525)
b1b779f2476 is described below
commit b1b779f2476b1dffd074582342b80cb21f6e353d
Author: gabriellafu <10...@users.noreply.github.com>
AuthorDate: Tue Jun 9 19:12:27 2026 -0400
MINOR: update AK/KS doc to (#22525)
- docs/getting-started/upgrade.md: Added KAFKA-20254 fix to the 4.2.1
notable changes section; updated the 4.2.0 note to say the fix is
available in 4.2.1.
- docs/streams/upgrade-guide.md: Updated the 4.2.0 note to say the fix
is available in 4.2.1.
- docs/streams/developer-guide/streams-rebalance-protocol.md: Updated
the migration warning to say the fix is available in 4.2.1.
Reviewers: Matthias J. Sax <ma...@confluent.io>
---
docs/getting-started/upgrade.md | 3 ++-
docs/streams/developer-guide/streams-rebalance-protocol.md | 2 +-
docs/streams/upgrade-guide.md | 2 +-
3 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/docs/getting-started/upgrade.md b/docs/getting-started/upgrade.md
index 12a114093ab..d9b35edcb39 100644
--- a/docs/getting-started/upgrade.md
+++ b/docs/getting-started/upgrade.md
@@ -61,6 +61,7 @@ Note: Apache Kafka 4.3 only supports KRaft mode - ZooKeeper mode has been remove
* Includes a fix for a critical deadlock in the [KIP-932](https://cwiki.apache.org/confluence/x/4hA0Dw) Share Group path ([KAFKA-20505](https://issues.apache.org/jira/browse/KAFKA-20505)).
* Includes a fix for a rolling upgrade issue ([KAFKA-20322](https://issues.apache.org/jira/browse/KAFKA-20322)) that could cause `UnsupportedVersionException` for clusters using transactional producers.
+ * Includes a fix for a critical broker-side bug in the offline migration code for the Streams Rebalance Protocol ([KAFKA-20254](https://issues.apache.org/jira/browse/KAFKA-20254)). Migrations from classic to streams groups are now safe starting with 4.2.1.
## Upgrading to 4.2.0
@@ -81,7 +82,7 @@ Note: Apache Kafka 4.2 only supports KRaft mode - ZooKeeper mode has been remove
* The `--max-partition-memory-bytes` option in `kafka-console-producer` is deprecated and will be removed in Kafka 5.0. Please use `--batch-size` instead.
* Queues for Kafka ([KIP-932](https://cwiki.apache.org/confluence/x/4hA0Dw)) is production-ready in Apache Kafka 4.2. This feature introduces a new kind of group called share groups, as an alternative to consumer groups. Consumers in a share group cooperatively consume records from topics, without assigning each partition to just one consumer. Share groups also introduce per-record acknowledgement and counting of delivery attempts. Use share groups in cases where records are processed [...]
- * The Streams Rebalance Protocol ([KIP-1071](https://cwiki.apache.org/confluence/display/KAFKA/KIP-1071%3A+Streams+Rebalance+Protocol)) is now production-ready for its core feature set. This broker-driven rebalancing system designed specifically for Kafka Streams applications provides faster, more stable rebalances and better observability. For more information about the supported feature set, usage, and migration, please refer to the [Streams developer guide](/{version}/streams/develo [...]
+ * The Streams Rebalance Protocol ([KIP-1071](https://cwiki.apache.org/confluence/display/KAFKA/KIP-1071%3A+Streams+Rebalance+Protocol)) is now production-ready for its core feature set. This broker-driven rebalancing system designed specifically for Kafka Streams applications provides faster, more stable rebalances and better observability. For more information about the supported feature set, usage, and migration, please refer to the [Streams developer guide](/{version}/streams/develo [...]
* The `org.apache.kafka.common.header.internals.RecordHeader` class has been updated to be read thread-safe. See [KIP-1205](https://cwiki.apache.org/confluence/x/nYmhFg) for details. In other words, each individual `Header` object within a `ConsumerRecord`'s `headers` can now be safely read from multiple threads concurrently.
* The `org.apache.kafka.disallowed.login.modules` config was deprecated. Please use the `org.apache.kafka.allowed.login.modules` instead.
* The `remote.log.manager.thread.pool.size` config was deprecated. Please use the `remote.log.manager.follower.thread.pool.size` instead.
diff --git a/docs/streams/developer-guide/streams-rebalance-protocol.md b/docs/streams/developer-guide/streams-rebalance-protocol.md
index dc84182bf10..a097bfd4c52 100644
--- a/docs/streams/developer-guide/streams-rebalance-protocol.md
+++ b/docs/streams/developer-guide/streams-rebalance-protocol.md
@@ -254,4 +254,4 @@ Similarly, you can convert a streams group back to a classic group by following
**Warning:** Online migration (migrating while the application is running) is not available in this version. Plan for a maintenance window when migrating between protocols.
-**Warning:** Due to a critical broker-side bug in the offline migration code ([KAFKA-20254](https://issues.apache.org/jira/browse/KAFKA-20254)), we recommend against doing migrations from classic to streams groups in 4.2.0. Newly created streams groups are not impacted. The fix will be targeted for a future release.
+**Warning:** Due to a critical broker-side bug in the offline migration code ([KAFKA-20254](https://issues.apache.org/jira/browse/KAFKA-20254)), we recommend against doing migrations from classic to streams groups in 4.2.0. Newly created streams groups are not impacted. The fix is available in 4.2.1.
diff --git a/docs/streams/upgrade-guide.md b/docs/streams/upgrade-guide.md
index fd3be2e2a9c..f8da6579970 100644
--- a/docs/streams/upgrade-guide.md
+++ b/docs/streams/upgrade-guide.md
@@ -139,7 +139,7 @@ This release marks the General Availability for the core functionality detailed
For more information about the feature set, design, usage and migration,
please refer to the [developer guide](/{version}/streams/developer-guide/streams-rebalance-protocol).
-**Note:** Due to a critical broker-side bug in the offline migration code ([KAFKA-20254](https://issues.apache.org/jira/browse/KAFKA-20254)), we recommend against doing migrations from classic to streams groups in 4.2.0. Newly created streams groups are not impacted. The fix will be targeted for a future release.
+**Note:** Due to a critical broker-side bug in the offline migration code ([KAFKA-20254](https://issues.apache.org/jira/browse/KAFKA-20254)), we recommend against doing migrations from classic to streams groups in 4.2.0. Newly created streams groups are not impacted. The fix is available in 4.2.1.
### Other changes