[
https://issues.apache.org/jira/browse/KAFKA-16412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878971#comment-17878971
]
Chia-Ping Tsai commented on KAFKA-16412:
----------------------------------------
[~gendong1] sorry for late response. the metadata change (topic creation) is
not a atomic operation, so the other requests can "see" the intermediate state.
The case you described will create the topic by first request eventually, right?
> Uncreated topics is considered as created topics
> ------------------------------------------------
>
> Key: KAFKA-16412
> URL: https://issues.apache.org/jira/browse/KAFKA-16412
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 2.8.2, 3.6.0
> Reporter: mutu
> Priority: Major
> Attachments: AnotherClientOutput.txt, client1-3.6.png,
> client2-3.6.png, kafkaServer1.out, kafkaServer2.out, kafkaServer3.out,
> system1-3.6.log, system2-3.6.log, system3-3.6.log
>
>
> A client sends topic creation request to broker.
> Another client sends the same topic creation request to broker.
> The former request does not finish. However, the second client get
> TopicExistsException.
> The root cause may be that topic is registered in zookeeper, but the data is
> not persisted and topic is not transfer to the paritition. At this time,
> another client sends the same topic creation request that check the status of
> zookeeper. After finding the znode of topic, the creation failed.
> System logs are attached.
> Are there any comments to figure out this issues？ I will very appreciate them.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
