Prateek Agarwal created KAFKA-13788:
---------------------------------------
Summary: Creation of invalid dynamic config prevents further
creation of valid configs
Key: KAFKA-13788
URL: https://issues.apache.org/jira/browse/KAFKA-13788
Project: Kafka
Issue Type: Bug
Components: config
Affects Versions: 2.8.0
Reporter: Prateek Agarwal
Kafka currently allows creating an unknown dynamic config without any errors.
But it errors when next valid dynamic config gets created.
This can be seen locally in a cluster by creating a wrong config
{{log.cleaner.threadzz}} which was preventing creation of the valid config
later {{log.cleaner.threads}}.
{code}
# Invalid config 'log.cleaner.threadzz' gets created without issues
$ ./bin/kafka-configs.sh --bootstrap-server localhost:9092 --alter --add-config
log.cleaner.threadzz=2 --entity-type brokers --entity-default 2>1
Completed updating default config for brokers in the cluster.
{code}
Now when a valid config is added, {{kafka-configs.sh}} errors out:
{code}
$ ./bin/kafka-configs.sh --bootstrap-server localhost:9092 --alter --add-config
log.cleaner.threads=2 --entity-type brokers --entity-default
All sensitive broker config entries must be specified for --alter, missing
entries: Set(log.cleaner.threadzz)
{code}
To fix this, one needs to first delete the incorrect config:
{code:java}
$ ./bin/kafka-configs.sh --bootstrap-server localhost:9092 --alter
--delete-config log.cleaner.threadzz --entity-type brokers --entity-default
{code}
But ideally, the invalid config should error out so that creation of the valid
config doesn't get prevented.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
