[
https://issues.apache.org/jira/browse/KAFKA-18230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot updated KAFKA-18230:
--------------------------------
Priority: Blocker (was: Major)
> admin client will fail immediately when the active controller changed
> ---------------------------------------------------------------------
>
> Key: KAFKA-18230
> URL: https://issues.apache.org/jira/browse/KAFKA-18230
> Project: Kafka
> Issue Type: Improvement
> Reporter: Luke Chen
> Assignee: Luke Chen
> Priority: Blocker
>
> When admin client starts up, it'll get the metadata of the cluster. And when
> the admin client sends request directly to the controller (via
> --bootstrap-controller), it'll send the request to the active controller. But
> if there is a leadership change in the controller after the metadata request
> and before the target request sent, the request will fail immediately with
> NOT_CONTROLLER error or NOT_LEADER_OR_FOLLOWER error. It's because the
> requests that need metadata log change must need to do on the active
> controller. Instead of failing immediately, the admin client should catch the
> error and retry the metadata update to send the request again.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
