Tom Bentley created KAFKA-10206:
-----------------------------------
Summary: 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
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)
