You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Jose Armando Garcia Sancio (Jira)" <ji...@apache.org> on 2022/08/16 14:47:00 UTC

[jira] [Updated] (KAFKA-13940) DescribeQuorum returns INVALID_REQUEST if not handled by leader

     [ https://issues.apache.org/jira/browse/KAFKA-13940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jose Armando Garcia Sancio updated KAFKA-13940:
-----------------------------------------------
    Fix Version/s: 3.3.0

> 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)