Do you still have the controller and state change logs from the time you originally tried to delete the topic?
On Tue, Jan 27, 2015 at 03:11:48PM -0800, Sumit Rangwala wrote: > I am using 0.8.2-beta on brokers 0.8.1.1 for client (producer and > consumers). delete.topic.enable=true on all brokers. replication factor is > < number of brokers. I see this issue with just one single topic, all other > topics are fine (creation and deletion). Even after a day it is still in > marked for deletion stage. Let me know what other information from the > brokers or the zookeepers can help me debug this issue. > > On Tue, Jan 27, 2015 at 9:47 AM, Gwen Shapira <gshap...@cloudera.com> wrote: > > > Also, do you have delete.topic.enable=true on all brokers? > > > > The automatic topic creation can fail if the default number of > > replicas is greater than number of available brokers. Check the > > default.replication.factor parameter. > > > > Gwen > > > > On Tue, Jan 27, 2015 at 12:29 AM, Joel Koshy <jjkosh...@gmail.com> wrote: > > > Which version of the broker are you using? > > > > > > On Mon, Jan 26, 2015 at 10:27:14PM -0800, Sumit Rangwala wrote: > > >> While running kafka in production I found an issue where a topic wasn't > > >> getting created even with auto topic enabled. I then went ahead and > > created > > >> the topic manually (from the command line). I then delete the topic, > > again > > >> manually. Now my broker won't allow me to either create *the* topic or > > >> delete *the* topic. (other topic creation and deletion is working fine). > > >> > > >> The topic is in "marked for deletion" stage for more than 3 hours. > > >> > > >> $ bin/kafka-topics.sh --zookeeper zookeeper1:2181/replication/kafka > > --list > > >> --topic GRIFFIN-TldAdFormat.csv-1422321736886 > > >> GRIFFIN-TldAdFormat.csv-1422321736886 - marked for deletion > > >> > > >> If this is a known issue, is there a workaround? > > >> > > >> Sumit > > > > >
