Re: Deleting a topic without delete.topic.enable=true?

If it issues topic metadata requests to find out what brokers the topic partitions live on (so it can make specific requests, like offsets, or getting JMX metrics from those brokers for the partitions), then it could easily have caused this. We’ve seen this behavior from multiple types of

Re: Deleting a topic without delete.topic.enable=true?

I wonder if datadog monitoring triggers that behavior. That's the only other piece of our infrastructure that may have been talking to that topic. On Mon, Dec 12, 2016 at 12:40 AM, Surendra , Manchikanti < surendra.manchika...@gmail.com> wrote: > If "auto.create.topics.enable" is set to true in

Re: Deleting a topic without delete.topic.enable=true?

If "auto.create.topics.enable" is set to true in your configurations , any producer/consumer or fetch request will create the topic again. Set it to false and delete the topic. -- Surendra Manchikanti On Sat, Dec 10, 2016 at 10:59 AM, Todd Palino wrote: > Are you running

Re: Deleting a topic without delete.topic.enable=true?

Are you running something else besides the consumers that would maintain a memory of the topics and potentially recreate them by issuing a metadata request? For example, Burrow (the consumer monitoring app I wrote) does this because it maintains a list of all topics in memory, and will end up

Re: Deleting a topic without delete.topic.enable=true?

On Fri, Dec 9, 2016 at 11:34 AM, Todd Palino wrote: > Given that you said you removed the log directories, and provided that when > you did the rmr on Zookeeper it was to the “/brokers/topics/(topic name)” > path, you did the right things for a manual deletion. It sounds like

Re: Deleting a topic without delete.topic.enable=true?

Given that you said you removed the log directories, and provided that when you did the rmr on Zookeeper it was to the “/brokers/topics/(topic name)” path, you did the right things for a manual deletion. It sounds like you may have a consumer (or other client) that is recreating the topic. Do you

Re: Deleting a topic without delete.topic.enable=true?

Any chance the consumer process that consumes from that topic is still running while you are doing all this? --Vahid From: Tim Visher <tim.vis...@gmail.com> To: users@kafka.apache.org Date: 12/09/2016 08:26 AM Subject: Re: Deleting a topic without delete.topic.enable=true

Re: Deleting a topic without delete.topic.enable=true?

I did all of that because setting delete.topic.enable=true wasn't effective. We set that across every broker, restarted them, and then deleted the topic, and it was still stuck in existence. On Fri, Dec 9, 2016 at 11:11 AM, Ali Akhtar wrote: > You need to also delete /

Re: Deleting a topic without delete.topic.enable=true?

You need to also delete / restart zookeeper, its probably storing the topics there. (Or yeah, just enable it and then delete the topic) On Fri, Dec 9, 2016 at 9:09 PM, Rodrigo Sandoval wrote: > Why did you do all those things instead of just setting >

Re: Deleting a topic without delete.topic.enable=true?

Why did you do all those things instead of just setting delete.topic.enable=true? On Dec 9, 2016 13:40, "Tim Visher" wrote: > Hi Everyone, > > I'm really confused at the moment. We created a topic with brokers set to > delete.topic.enable=false. > > We now need to delete

Deleting a topic without delete.topic.enable=true?

Hi Everyone, I'm really confused at the moment. We created a topic with brokers set to delete.topic.enable=false. We now need to delete that topic. To do that we shut down all the brokers, deleted everything under log.dirs and logs.dir on all the kafka brokers, `rmr`ed the entire chroot that