[
https://issues.apache.org/jira/browse/KAFKA-10206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17257114#comment-17257114
]
Ismael Juma commented on KAFKA-10206:
-------------------------------------
One thing to keep in mind is that the quorum controller (i.e. kip-500) will
have a new mechanism instead of UpdateMetadata request. It may make sense to
focus on making sure that this new approach handles these cases well. I know
[~cmccabe] is aware of the issue, but not sure if the solution was clearly
outlined yet.
> 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)
