You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Chia-Ping Tsai (Jira)" <ji...@apache.org> on 2026/01/05 18:12:00 UTC
[jira] [Resolved] (KAFKA-18928) Support to dynamically change config for specific controller
[ https://issues.apache.org/jira/browse/KAFKA-18928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chia-Ping Tsai resolved KAFKA-18928.
------------------------------------
Fix Version/s: 4.3.0
Resolution: Fixed
> Support to dynamically change config for specific controller
> ------------------------------------------------------------
>
> Key: KAFKA-18928
> URL: https://issues.apache.org/jira/browse/KAFKA-18928
> Project: Kafka
> Issue Type: Task
> Reporter: Chia-Ping Tsai
> Assignee: fujian
> Priority: Major
> Fix For: 4.3.0
>
>
> see the discussion: [https://github.com/apache/kafka/pull/19100#discussion_r1981121079]
> Currently. It only support dynamically changing configs for a specific *static* quorum controller.
> h3. Test Environment
> Dynamic quorum environment:
> {{_controller.quorum.bootstrap.servers=ip1:port,ip2:port,ip3:port_ }}
> Static quorum environment:
> _{{controller.quorum.voters=id1@ip1:port,id2@ip2:port,id3@ip3:port}}_
> h3. Test command
> _{{./kafka-configs.sh--bootstrap-controller ip:port --entity-type brokers --entity-name 1001 --command-config /etc/kafka/admin_config.properties --alter --add-config max.connections=10086}}_
> Completed updating config for broker 1001.
> h3. Verify command
> _{{./kafka-configs.sh --bootstrap-controller ip:port --entity-type brokers --entity-name 1001 --command-config /etc/kafka/admin_config.properties --describe --all |grep -E 'max.connections|node'}}_
> max.connections=10086 sensitive=false synonyms=\{DYNAMIC_BROKER_CONFIG:max.connections=100005, DEFAULT_CONFIG:max.connections=2147483647}
> node.id=1001 sensitive=false synonyms=\{STATIC_BROKER_CONFIG:node.id=1001}
> h3. Test result
> The issue on the dynamic quorum:
> {{_java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.BrokerIdNotRegisteredException: No node with id 1001 found.
> at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:396)
> at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2096)
> at org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:173)
> at kafka.admin.ConfigCommand$.alterResourceConfig(ConfigCommand.scala:425)
> at kafka.admin.ConfigCommand$.alterConfig(ConfigCommand.scala:192)
> at kafka.admin.ConfigCommand$.processCommand(ConfigCommand.scala:165)
> at kafka.admin.ConfigCommand$.main(ConfigCommand.scala:87)
> at kafka.admin.ConfigCommand.main(ConfigCommand.scala)
> Caused by: org.apache.kafka.common.errors.BrokerIdNotRegisteredException: No node with id 1001 found._}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)