[jira] [Commented] (KAFKA-4675) Subsequent CreateTopic command could be lost after a DeleteTopic command

["huxi (JIRA)" <ji...@apache.org>]

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

huxi commented on KAFKA-4675:
-----------------------------

Seems deleting '/brokers/topics/<topic>' comes fourth from the bottom during the topic deletion while creating it comes top front in createTopic logic, did you encounter the TopicExistsException that failed the creation?

> Subsequent CreateTopic command could be lost after a DeleteTopic command
> ------------------------------------------------------------------------
>
>                 Key: KAFKA-4675
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4675
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Guozhang Wang
>              Labels: admin
>
> This is discovered while investigating KAFKA-3896: If an admin client sends a delete topic command and a create topic command consecutively, even if it wait for the response of the previous command before issuing the second, there is still a race condition that the create topic command could be "lost".
> This is because currently these commands are all asynchronous as defined in KIP-4, and controller will return the response once it has written the corresponding data to ZK path, which can be handled by different listener threads at different paces, and if the thread handling create is faster than the other, the executions could be effectively re-ordered.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)