This is an automated email from the ASF dual-hosted git repository.
lucasbru pushed a commit to branch markdown
in repository https://gitbox.apache.org/repos/asf/kafka-site.git
The following commit(s) were added to refs/heads/markdown by this push:
new 433029339c Improve wording of KAFKA-20254 migration warning (#827)
433029339c is described below
commit 433029339cce2ab6b94a71836287c981e9f9e8f8
Author: Lucas Brutschy <[email protected]>
AuthorDate: Tue Mar 10 12:48:18 2026 +0100
Improve wording of KAFKA-20254 migration warning (#827)
---
content/en/42/getting-started/upgrade.md | 2 +-
content/en/42/streams/developer-guide/streams-rebalance-protocol.md | 2 +-
content/en/42/streams/upgrade-guide.md | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/en/42/getting-started/upgrade.md
b/content/en/42/getting-started/upgrade.md
index 4b353c2419..bdbf058632 100644
--- a/content/en/42/getting-started/upgrade.md
+++ b/content/en/42/getting-started/upgrade.md
@@ -34,7 +34,7 @@ type: docs
* 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/content/en/42/streams/developer-guide/streams-rebalance-protocol.md
b/content/en/42/streams/developer-guide/streams-rebalance-protocol.md
index df019a1086..dc84182bf1 100644
--- a/content/en/42/streams/developer-guide/streams-rebalance-protocol.md
+++ b/content/en/42/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. Users planning to migrate a
classic group to the new protocol should wait for a future release that
includes the fix.
+**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.
diff --git a/content/en/42/streams/upgrade-guide.md
b/content/en/42/streams/upgrade-guide.md
index 8e5145d6f8..e148f24295 100644
--- a/content/en/42/streams/upgrade-guide.md
+++ b/content/en/42/streams/upgrade-guide.md
@@ -72,7 +72,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. Users planning to migrate a
classic group to the new protocol should wait for a future release that
includes the fix.
+**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.
### Other changes
