Gillian Wang created KAFKA-21519:
------------------------------------
Summary: Removing a startup-loaded broker setting through dynamic
DELETE leaves the old value effective
Key: KAFKA-21519
URL: https://issues.apache.org/jira/browse/KAFKA-21519
Project: Kafka
Issue Type: Bug
Affects Versions: 4.3.2
Reporter: Gillian Wang
# Clarify cluster-wide DELETE semantics for startup-loaded broker configuration
In a Strimzi-managed Kafka 4.3.2 cluster, removing a startup-loaded broker
setting from the desired configuration leaves the old setting effective after a
successful cluster-wide dynamic DELETE.
## Observed behavior
1. Start three brokers with `compression.type=zstd` in their configuration
files.
2. Remove `compression.type` from the Kafka resource. Strimzi removes it from
the generated broker configuration files and sends a cluster-wide dynamic
DELETE without restarting the brokers.
3. Neither the dynamic cluster defaults nor the per-broker dynamic
configurations contain a `compression.type` override after removal.
4. All three brokers still report `compression.type=zstd` from
`STATIC_BROKER_CONFIG`.
5. Produce new records with producer `compression.type=none`. Inspection of the
stored batches shows that the brokers still apply `zstd`, so this is not only a
stale DescribeConfigs result.
6. Restart the brokers one at a time with the updated configuration files. Each
restarted broker switches to the default `producer`; subsequent records are no
longer compressed when the producer uses `none`.
The reported effective configuration before restart is:
```text
compression.type=zstd sensitive=false
synonyms=\{STATIC_BROKER_CONFIG:compression.type=zstd,
DEFAULT_CONFIG:compression.type=producer}
```
After restart:
```text
compression.type=producer sensitive=false
synonyms=\{DEFAULT_CONFIG:compression.type=producer}
```
## Questions
Could you confirm is retaining the startup-loaded static value the intended
behavior after a cluster-wide DELETE when no dynamic override remains?
A Strimzi maintainer suggested this might be a Kafka bug or breaking change. We
are asking for confirmation of the API semantics.
## References
Original discussion:
https://github.com/strimzi/strimzi-kafka-operator/issues/13355
Broker configuration documentation:
https://github.com/apache/kafka/blob/trunk/docs/configuration/broker-configs.md
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)