It seems the proposed workflow is the following. 1. Client issues a global config update request to the broker. 2. Broker writes the new config to ZK. 3. Controller picks up the changes from ZK. 4. Controller propagates the config changes to all brokers.
Do we need to add a new request/response to propagate the config changes? Also, this logic is a bit different from how per topic config changes works: each broker reads from ZK directly. It would be good to make them consistent. Thanks, Jun On Wed, Jan 21, 2015 at 10:34 PM, Joe Stein <joe.st...@stealth.ly> wrote: > Created a KIP > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-5+-+Broker+Configuration+Management > > JIRA https://issues.apache.org/jira/browse/KAFKA-1786 > > /******************************************* > Joe Stein > Founder, Principal Consultant > Big Data Open Source Security LLC > http://www.stealth.ly > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > ********************************************/ >
