You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Rajini Sivaram (JIRA)" <ji...@apache.org> on 2019/08/16 07:44:00 UTC

[jira] [Resolved] (KAFKA-8592) Broker Dynamic Configuration fails to resolve variables as per KIP-421

     [ https://issues.apache.org/jira/browse/KAFKA-8592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajini Sivaram resolved KAFKA-8592.
-----------------------------------
    Resolution: Fixed

> Broker Dynamic Configuration fails to resolve variables as per KIP-421 
> -----------------------------------------------------------------------
>
>                 Key: KAFKA-8592
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8592
>             Project: Kafka
>          Issue Type: Bug
>          Components: config
>    Affects Versions: 2.3.0
>            Reporter: TEJAL ADSUL
>            Priority: Major
>             Fix For: 2.3.1
>
>
> In add/alter new configs for DynamicConfigs it does not go through the KafkaConfig
> eg: bin/kafka-configs --bootstrap-server localhost:9092 --entity-type brokers --entity-name 0 --alter --add-config log.cleaner.threads=2
> However the bootstrap-server localhost is parsed through the kafkaConfig to create the adminClient but not the log.cleaner.thread. 
> As the configs are not parsed using the KafkaConfig if we pass variables in configs they are bot resolved at run time.
> In order to resolve the variables in alterConfig/addConfigs flow we need to parse the new configs  using KafkaConfig before they are parsed.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)