Versions Compared

Old Version 8

changes.mady.by.user Andrii Biletskyi

Saved on

compared with

New Version Current

changes.mady.by.user Ewen Cheslack-Postava

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Brokers should be able to pull from a meta data store to get their configurations.

Status

Current state:  "Under Discussion" Superseded by KIP-21

Discussion thread: here

JIRA: here

...

ConfigChangeRequest => [ConfigData]
ConfigData => ConfigKey ConfigValue
  
ConfigKey => string
ConfigValue => string

Response:

ConfigChangeResponse => ErrorCode
ErrorCode => int16

To change global configuration:

  1. User issues ChangeConfigRequest to Controller with global configuration that needs to be updated
  2. Controller fetches current global configuration from zk, merges with supplied and validates merged config (this part relies on KAFKA-1845)
  3. If successful, configuration is updated in zk
  4. Once broker is restarted new New global configuration is applied to it picked up by broker once restarted

Compatibility, Deprecation, and Migration Plan

  • When will we remove the existing behavior?

I don't think we have to decide that nowIn 0.8.3 we will still support the property files but it will be deprecated and we will then remove support for property files in 0.9.0.

Rejected Alternatives

If there are alternative ways of accomplishing the same thing, what were they? The purpose of this section is to motivate why the design is the way it is and not some other way.