Andrew Schofield created KAFKA-18904:
----------------------------------------
Summary: Listing of configs for dynamically created resources is
mysterious
Key: KAFKA-18904
URL: https://issues.apache.org/jira/browse/KAFKA-18904
Project: Kafka
Issue Type: Improvement
Reporter: Andrew Schofield
The `kafka-configs.sh` tool can be used to set configurations on dynamically
created resources such as groups and client metrics. However, the way that
listing of the configs works is unhelpful.
bin/kafka-configs.sh --bootstrap-server localhost:9092 --alter --group G1
--add-config consumer.heartbeat.interval.ms=10000
* This defines the config consumer.heartbeat.interval.ms
bin/kafka-configs.sh --bootstrap-server localhost:9092 --describe --entity-type
groups
* This only describes the configs of groups that actually exist, as will happen
when the group actually has started being used.
bin/kafka-configs.sh --bootstrap-server localhost:9092 --describe --entity-type
groups --entity-name G1
* This actually displays the configs for G1.
The problem is that using `--describe` with no entity name, the tool lists the
resources (the groups) not the configs. As a result, if you define configs in
preparation for the use of groups in the future, you need to remember what you
created. You cannot list the groups for which configs are defined, only the
groups which actually exist from the point of view of the group coordinator.
Client metrics are a bit better because there is at least an RPC for listing
the client metrics resources.
There is a second class of related problem.
bin/kafka-configs.sh --bootstrap-server localhost:9092 --describe --entity-type
groups --entity-name DOESNOTEXIST
* This does not return an error for a non-existent resource.
bin/kafka-configs.sh --bootstrap-server localhost:9092 --describe --entity-type
client-metrics --entity-name DOESNOTEXIST
* This does not return an error for a non-existent resource.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
