This is an automated email from the ASF dual-hosted git repository.
schofielaj pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/trunk by this push:
new 1da46fb1fed MINOR: Share group config upgrade docs (#21589)
1da46fb1fed is described below
commit 1da46fb1fed96cf8e5ac3929006b1e0eb435e97f
Author: Andrew Schofield <[email protected]>
AuthorDate: Thu Feb 26 17:21:42 2026 +0000
MINOR: Share group config upgrade docs (#21589)
Add a note to the upgrading docs for users with clusters of fewer than 3
brokers. Share groups introduce a new internal topic whose default
configuration assumes 3 or more brokers.
This will be cherry-picked back to the 4.2 branch for inclusion in
4.2.1.
Reviewers: Apoorv Mittal <[email protected]>
---
docs/getting-started/upgrade.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/docs/getting-started/upgrade.md b/docs/getting-started/upgrade.md
index 22a4b0f6524..9aab59ddd52 100644
--- a/docs/getting-started/upgrade.md
+++ b/docs/getting-started/upgrade.md
@@ -43,6 +43,8 @@ type: docs
### Upgrading Servers to 4.2.0 from any version 3.3.x through 4.1.x
+ * If you wish to use share groups in a cluster with fewer than 3 brokers,
you must set the broker configurations
`share.coordinator.state.topic.replication.factor` and
`share.coordinator.state.topic.min.isr` to 1 before you start using share
groups. This is because share groups make use of a new internal topic called
`__share_group_state` which is automatically created when you first use share
groups. In common with the other internal topics, the default configuration
uses 3 replicas a [...]
+
### Notable changes in 4.2.0
* 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.
