Thanks for your prompt response.
In my check for topicExists i will add a check for topic in
DeleteTopicsPath.
On Mon, Mar 23, 2015 at 8:21 PM, Harsha wrote:
> Just to be clear, one needs to stop producers and consumers that
> writing/reading from a topic “test” if they are trying to delete t
Just to be clear, one needs to stop producers and consumers that
writing/reading from a topic “test” if they are trying to delete that specific
topic “test”. Not all producers and clients.
--
Harsha
On March 23, 2015 at 10:13:47 AM, Harsha (harsh...@fastmail.fm) wrote:
Currently we have auto.c
Currently we have auto.create.topics.enable set to true by default. If this is
set true any one who is making TopicMetadataRequest can create a topic . As
both producers and consumers can send TopicMetadataRequest which will create a
topic if the above config is true. So while doing deletion if
What happens when producers or consumers are running while the topic
deleting is going on?
On Mon, Mar 23, 2015 at 10:02 AM, Harsha wrote:
> DeleteTopic makes a node in zookeeper to let controller know that there is
> a topic up for deletion. This doesn’t immediately delete the topic it can
> ta
DeleteTopic makes a node in zookeeper to let controller know that there is a
topic up for deletion. This doesn’t immediately delete the topic it can take
time depending if all the partitions of that topic are online and brokers are
available as well. Once all the Log files deleted zookeeper nod
