kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-4675) Subsequent CreateTopic command could be lost after a DeleteTopic command
Date Thu, 16 Nov 2017 13:27:01 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-4675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ismael Juma resolved KAFKA-4675.
--------------------------------
    Resolution: Duplicate

KAFKA-6098 is the same issue and has more information.

> 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.4.14#64029)

Mime
View raw message