This page is meant as a template for writing a KIP. To create a KIP choose Tools->Copy on this page and modify with your content and replace the heading with the next KIP number and a description of your issue. Replace anything in italics with your own description.

Status

Current state: WIP

Discussion thread:

JIRA: 

Motivation

Currently, all cluster configuration is managed via property files read by the brokers on startup. There is no mechanism to change broker configuration without having to do a rolling restart of the entire cluster. Additionally, there is no way to model configuration per-client i.e. quotas, permissions etc.

This proposal attempts to build a unified mechanism for modeling configuration across various entities like topics, clients and brokers.

Public Interfaces

TODO

Proposed Changes

Compatibility, Deprecation, and Migration Plan

• What impact (if any) will there be on existing users?
• If we are changing behavior how will we phase out the older behavior?
• If we need special migration tools, describe them here.
• When will we remove the existing behavior?

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.