如何获取Kafka集群当前配置？配置修改后是否需重启服务？

Hey there! Let's work through your Kafka config confusion step by step.

First, let's clarify why your kafka-configs.sh command is returning empty output: that tool specifically shows dynamic configuration overrides—settings you've applied directly via kafka-configs.sh that overwrite the static values in server.properties. Since you used Puppet to modify the static config files, this command won't show those changes (unless you've also set dynamic overrides).

Here are reliable ways to get the currently active Kafka broker configuration:

1. Check the Kafka server logs #

Kafka logs all active configuration values when it starts up. Look for entries starting with Config values or Loaded properties from in your server log file (usually located at /var/log/kafka/server.log or similar, depending on your setup).

You can grep for this with:

grep "Config values" /path/to/kafka/logs/server.log

This will give you a complete dump of every configuration the broker is using, including both static file settings and any dynamic overrides.

2. Use JMX to inspect live configuration #

Kafka exposes its current configuration via JMX. You can use tools like jconsole, jvisualvm, or the command-line kafka-run-class utility to access these metrics:

Command-line approach: #

Run this from your Kafka bin directory:

./kafka-run-class.sh kafka.tools.JmxTool --object-name kafka.server:type=kafkaConfig,name=brokerConfig --attributes all

This will output all active configuration key-value pairs directly in your terminal.

GUI approach: #

• Open jconsole and connect to your Kafka broker's JMX port (default is 9999, check server.properties for jmx.port if you've changed it).
• Navigate to the kafka.server domain, find the kafkaConfig MBean named brokerConfig, and you'll see all current config values listed.

3. Verify static config changes and service status #

Since you used Puppet to modify static config files (like server.properties), most core Kafka settings (e.g., listeners, broker.id, log.dirs) require a broker restart to take effect. A few exceptions (like log4j logging configs) might support dynamic reloading, but this is rare.

To confirm if your changes are active:

• Check the modified timestamp of your server.properties file and compare it to the Kafka process start time (use ps aux | grep kafka to see when the broker launched).
• If the process started before the config file was modified, you'll need to restart the Kafka service (e.g., systemctl restart kafka for systemd setups) to load the new config.

4. Why you're not seeing config in ZooKeeper #

Older Kafka versions (pre-0.10.x) stored some broker configuration in ZooKeeper, but modern Kafka releases have moved almost all config management to local files or dynamic configuration APIs. So not finding anything in ZK is expected behavior for newer clusters—no need to worry about that.

Quick recap #

• kafka-configs.sh only shows dynamic overrides, not static file configs.
• Use server logs or JMX to get the full active config.
• Most static config changes require a Kafka restart to take effect.

内容的提问来源于stack exchange，提问作者Acampoh