Hi Jeff,
Are you seeing any errors in state-change.log or controller.log
after issuing kafka-topics.sh --delete command.
There is another known issue is if you have auto.topic.enable.create =
true (this is true by default) your consumer or producer can re-create
the topic. So try stopping any of your consumers or producers run the
delete topic command again.
-Harsha
On Wed, Mar 4, 2015, at 10:28 AM, Jeff Schroeder wrote:
> So I've got 3 kafka brokers that were started with delete.topic.enable
> set
> to true. When they start, I can see in the logs that the property was
> successfully set. The dataset in each broker is only approximately 2G
> (per
> du). When running kafaka-delete.sh with the correct arguments to delete
> all
> of the topics, it says that the topic is marked for deletion. When
> running
> again, it says that the topic is already marked for deletion.
>
> From reading the documentation, my understanding is that one of the 10
> (default) background threads would eventually process the deletes, and
> clean up both the topics in zookeeper, and the actual data on disk. In
> reality, it didnt seem to delete the data on disk or remove anything in
> zookeeper.
>
> What is the correct way to remove a topic in kafka 0.8.2 and what is the
> expected timeframe for that to complete expected to be? My "solution" was
> stopping the brokers and rm -rf /var/lib/kafka/*, but that is clearly a
> very poor one once we are done testing our kafka + storm setup.
>
> --
> Jeff Schroeder
>
> Don't drink and derive, alcohol and analysis don't mix.
> http://www.digitalprognosis.com
