Page History

...

Take AlterConfig as an example to understand the changes we are making.

Change

...

How ZK Mutation Request

...

Routs

The new simple routing change makes sure only controller needs to write to ZK, while other broker shall just wait for the metadata update from ZK notification eventually. As we have the source of truth configs stored in ZK still, any re-election of controller shall be safe.

For admin RPCs who are currently sending directly to the controller, brokers should support the proxy of such requests, with a revised update path during the bridge release (take AlterConfig as an example):

1. The admin client issues an (Incremental)AlterConfig request to a random broker

2. The broker redirects the request to the controller

3. The controller updates the config, and store it in ZK

4. If #3 successful, returns to the proxy broker

5. The proxy broker returns to the client as success

6. ZK update will be propagated towards all affected brokers in the cluster

...