[
https://issues.apache.org/jira/browse/KAFKA-16412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902509#comment-17902509
]
mutu commented on KAFKA-16412:
------------------------------
[~chia7712] Yes, Kafka finish the first request eventually. My concern is that
the second client will fail to write and read the topic before the topic is
actually built in described case. This scenario confuses the second client and
reduce the usability of Kafka.
> 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)
