[ 
https://issues.apache.org/jira/browse/KAFKA-17094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864980#comment-17864980
 ] 

Igor Soarez commented on KAFKA-17094:
-------------------------------------

I agree it makes sense to make this information available through RPCs, but the 
{{Quorum}} is probably not the right place to represent registered (but 
inactive) brokers – Quorum represents only the Raft-like part of the cluster. I 
think it would make more sense to add a new field to 
{{{}DescribeClusterResponse{}}}. I guess {{handleDescribeCluster}} filters out 
inactive brokers to preserve the ZK-mode behavior.

> Make it possible to list registered KRaft nodes in order to know which nodes 
> should be unregistered
> ---------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-17094
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17094
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 3.7.1
>            Reporter: Jakub Scholz
>            Priority: Major
>
> Kafka seems to require nodes that are removed from the cluster to be 
> unregistered using the Kafka Admin API. If they are unregistred, that you 
> might run into problems later. For example, after upgrade when you try to 
> bump the KRaft metadata version, you might get an error like this:
>  
> {code:java}
> g.apache.kafka.common.errors.InvalidUpdateVersionException: Invalid update 
> version 19 for feature metadata.version. Broker 3002 only supports versions 
> 1-14 {code}
> In this case, 3002 is an old node that was removed before the upgrade and 
> doesn't support the KRaft metadata version 19 and blocks the metadata update.
>  
> However, it seems to be impossible to list the registered nodes in order to 
> unregister them:
>  * The describe cluster metadata request in the Admin API seems to return 
> only the IDs of running brokers
>  * The describe metadata quorum command seems to list the removed nodes in 
> the list of observers. But it does so only until the controller nodes are 
> restarted.
> If Kafka expects the inactive nodes to be registered, it should provide a 
> list of the registered nodes so that it can be checked what nodes to 
> unregister.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to