[jira] [Commented] (KAFKA-10206) Admin can transiently return incorrect results about topics

["Colin McCabe (Jira)" <ji...@apache.org>]

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

Colin McCabe commented on KAFKA-10206:
--------------------------------------

This is fixed in KRaft mode, since the broker will be fenced until it catches up with metadata. I suppose we should leave this JIRA open until we retire ZK mode, though (hopefully 4.0...)

> Admin can transiently return incorrect results about topics
> -----------------------------------------------------------
>
>                 Key: KAFKA-10206
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10206
>             Project: Kafka
>          Issue Type: Bug
>          Components: admin, core
>            Reporter: Tom Bentley
>            Assignee: Tom Bentley
>            Priority: Major
>
> When a broker starts up it can handle metadata requests before it has 
> received UPDATE_METADATA requests from the controller. 
> This manifests in the admin client via:
> * listTopics returning an empty list
> * describeTopics and describeConfigs of topics erroneously returning TopicOrPartitionNotFoundException
> I assume this also affects the producer and consumer, though since `UnknownTopicOrPartitionException` is retriable those clients recover.
> Testing locally suggests that the window for this happening is typically <1s.
> There doesn't seem to be any way for the caller of the Admin client to detect this situation.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)