[
https://issues.apache.org/jira/browse/KAFKA-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138979#comment-14138979
]
Neha Narkhede commented on KAFKA-1558:
--------------------------------------
[~sriharsha] Delete topic shouldn't be affected by the replica fetcher issue.
Have you let it stay as is and see if delete topic eventually completes? If
not, have you taken a thread dump to see where it halts, if at all?
For each of the tests above, an important scenario is a large number of topics
being actively written to and read from. For the tests, it is important to
create, say a 1000 topics, and run producers in parallel that write to those
1000 topics, consumers that consume and then introduce each of the failures
above. Delete topic should succeed even if there are writes/reads happening to
the topic.
> AdminUtils.deleteTopic does not work
> ------------------------------------
>
> Key: KAFKA-1558
> URL: https://issues.apache.org/jira/browse/KAFKA-1558
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.1.1
> Reporter: Henning Schmiedehausen
> Assignee: Sriharsha Chintalapani
> Priority: Blocker
> Fix For: 0.8.2
>
>
> the AdminUtils:.deleteTopic method is implemented as
> {code}
> def deleteTopic(zkClient: ZkClient, topic: String) {
> ZkUtils.createPersistentPath(zkClient,
> ZkUtils.getDeleteTopicPath(topic))
> }
> {code}
> but the DeleteTopicCommand actually does
> {code}
> zkClient = new ZkClient(zkConnect, 30000, 30000, ZKStringSerializer)
> zkClient.deleteRecursive(ZkUtils.getTopicPath(topic))
> {code}
> so I guess, that the 'createPersistentPath' above should actually be
> {code}
> def deleteTopic(zkClient: ZkClient, topic: String) {
> ZkUtils.deletePathRecursive(zkClient, ZkUtils.getTopicPath(topic))
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
