[
https://issues.apache.org/jira/browse/KAFKA-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577095#comment-14577095
]
Bogdan Popa commented on KAFKA-2231:
------------------------------------
I'm having the same situation.
It's a staging machine on AWS with one kafka broker and one zookeeper node. I'm
using kafka 8.2.1.
On --list all topics remain as "marked for deletion" even after multiple
restarts of kafka / zookeeper. It's worth noting that the actual files got
deleted but not for all topics.
Another thing that might be relevant is that I've obtained this server by
creating an image of an existing node form a production cluster and then
changing the config to make it it's own cluster.
delete.topic.enable is true
> Deleting a topic fails
> ----------------------
>
> Key: KAFKA-2231
> URL: https://issues.apache.org/jira/browse/KAFKA-2231
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.2.1
> Environment: Windows 8.1
> Reporter: James G. Haberly
> Priority: Minor
>
> delete.topic.enable=true is in config\server.properties.
> Using --list shows the topic "marked for deletion".
> Stopping and restarting kafka and zookeeper does not delete the topic; it
> remains "marked for deletion".
> Trying to recreate the topic fails with "Topic XXX already exists".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
