...

• Command line tools and arguments

Proposed Changes

You can keep using properties as you do today. If you decide to use the global configuration feature then only a few properties will be able to be overridden e.g. host and port. All other properties will either be default or set in the central meta store for retrieving the settings.

These changes use and are based on KAFKA-1845 (KafkaConfig should use ConfigDef).

The new proposed workflow is the following:

1. The broker is being started (entry point - Kafka.scala class)
2. The local configuration file server.properties is parsed
3. Global configuration settings (if present) are picked up from zookeeper
4. Global configuration take precedence over local except for predefined list (currently - brokerId, host, port, advertisedHost, advertisedPort)
5. KafkaServer is started with "merged" configuration

The global configuration is stored in the same format as topic-level configuration:

{

"version

Compatibility, Deprecation, and Migration Plan

...