[
https://issues.apache.org/jira/browse/KAFKA-13940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-13940.
-------------------------------------
Resolution: Fixed
> DescribeQuorum returns INVALID_REQUEST if not handled by leader
> ---------------------------------------------------------------
>
> Key: KAFKA-13940
> URL: https://issues.apache.org/jira/browse/KAFKA-13940
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Major
> Fix For: 3.3.0
>
>
> In `KafkaRaftClient.handleDescribeQuorum`, we currently return
> INVALID_REQUEST if the node is not the current raft leader. This is
> surprising and doesn't work with our general approach for retrying forwarded
> APIs. In `BrokerToControllerChannelManager`, we only retry after
> `NOT_CONTROLLER` errors. It would be more consistent with the other Raft APIs
> if we returned NOT_LEADER_OR_FOLLOWER, but that also means we need additional
> logic in `BrokerToControllerChannelManager` to handle that error and retry
> correctly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
