You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kafka.apache.org by ch...@apache.org on 2026/09/11 23:38:26 UTC
(kafka) branch trunk updated: MINOR: adding consumer group assignor name collide description in upgrade.md (#23439)
This is an automated email from the ASF dual-hosted git repository.
chia7712 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 0ffb4f5dd57 MINOR: adding consumer group assignor name collide description in upgrade.md (#23439)
0ffb4f5dd57 is described below
commit 0ffb4f5dd57c6af206e3d9f97a433dd15ebb6dfc
Author: gabriellafu <10...@users.noreply.github.com>
AuthorDate: Fri Sep 11 19:38:18 2026 -0400
MINOR: adding consumer group assignor name collide description in upgrade.md (#23439)
adding consumer group assignor name collide description in upgrade.md
Reviewers: Chia-Ping Tsai <ch...@gmail.com>
---
docs/getting-started/upgrade.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/docs/getting-started/upgrade.md b/docs/getting-started/upgrade.md
index 5161cc587db..4fc57a7139a 100644
--- a/docs/getting-started/upgrade.md
+++ b/docs/getting-started/upgrade.md
@@ -56,6 +56,7 @@ type: docs
* Controllers can now be unregistered from the cluster metadata. A new `kafka-cluster.sh unregister-controller` command and a `--unregister` flag on `kafka-metadata-quorum.sh remove-controller` are provided, backed by the new `Admin#unregisterController` API and the new `UnregisterController` RPC. This introduces the error code `CONTROLLER_ID_NOT_REGISTERED` (136) and requires metadata version `4.4-IV2` (`IBP_4_4_IV2`). For further details, please refer to [KIP-1312](https://cwiki.apac [...]
* A new client configuration, `bootstrap.resolve.timeout.ms`, controls how DNS resolution of `bootstrap.servers` is performed. The default value of `0` preserves the historical synchronous behavior. Setting a positive value opts into asynchronous bootstrap resolution: the client constructor returns immediately, `NetworkClient` retries DNS resolution up to the configured timeout, and failures are surfaced later as `BootstrapResolutionExceptions` from subsequent API calls. This failure i [...]
* For tiered-storage topics, time-based local retention (`local.retention.ms`) now uses a segment's last modified time as the age anchor when the segment's largest record timestamp is in the future. Previously such a segment was never removed by time-based retention (its future timestamp kept it perpetually within the retention window) and was only reclaimed once `local.retention.bytes` was breached, even though it had already been uploaded to remote storage. For further details, pleas [...]
+ * `group.consumer.assignors` no longer allows a custom assignor to reuse the name of a built-in assignor (e.g. `uniform`, `range`), even when it is configured on its own to intentionally replace the built-in's behavior. Such a configuration used to be accepted and now fails broker startup with a `ConfigException`. For further details, please refer to [KAFKA-20843](https://issues.apache.org/jira/browse/KAFKA-20843).
## Upgrading to 4.3.0