Debugging Kafka configuration precedence
I identify the topic, broker, and observed behavior, then inspect topic-level configuration and broker configuration separately. Kafka configuration is scoped: some settings are topic-level, some broker-level, and some client-side. A topic override or dynamic broker override may explain why behavior differs from a static configuration file. I verify the effective value and its source instead of assuming that the file on disk is authoritative.
Inspect topic overrides for settings such as retention.ms and cleanup.policy. If no override exists, confirm the inherited default for the installed version.
Inspect dynamic broker overrides as well as static configuration. Precedence and support depend on the setting and Kafka version.
Do not confuse broker settings with producer or consumer settings; client batching and fetch behavior are also controlled by client configuration.
Some changes apply dynamically, while others require a restart or affect only newly created resources. Verify the setting's documented behavior for the deployed version.
Common mistake: editing server.properties and assuming a running broker immediately uses the new value.
Configuration inspection options and supported dynamic settings have evolved. Validate command syntax and configuration sources against the installed release.
0-2 years experience
2-5 years experience
5-8 years experience
8+ years experience