Deleting topic is an on-going JIRA: KAFKA-330, and we are shooting for have
it checked in soon.
On Wed, Feb 5, 2014 at 3:59 PM, David Birdsong wrote:
> On Wed, Feb 5, 2014 at 2:22 PM, Robert Rodgers
> wrote:
>
> > this would be great to add to the operational section of the Kafka
> > documentat
On Wed, Feb 05, 2014 at 03:59:29PM -0800, David Birdsong wrote:
> On Wed, Feb 5, 2014 at 2:22 PM, Robert Rodgers wrote:
>
> > this would be great to add to the operational section of the Kafka
> > documentation.
> >
>
> So is this a way to delete topics? Does this work?
Not really - (I'm assumi
Yes I think so - max fetch size defaults to 1 MB and num-replica
fetchers to one which should be sufficient for most people. Setting
those higher would typically lead to higher memory usage when there
are a large number of topics and with num-fetchers it would multiply
the number of socket connecti
On Wed, Feb 5, 2014 at 2:22 PM, Robert Rodgers wrote:
> this would be great to add to the operational section of the Kafka
> documentation.
>
So is this a way to delete topics? Does this work?
>
> On Feb 5, 2014, at 2:18 PM, Andrew Otto wrote:
>
> >> - Increasing num.replica.fetchers (defaul
Do we have the right default?
-Jay
On Wed, Feb 5, 2014 at 2:04 PM, Joel Koshy wrote:
>
> > topics are all caught up, but I have one high volume topic (around
> > 40K msgs/sec) that is taking much longer. I just took a few samples
> > of Replica-MaxLag to see how long it would take to catch up
this would be great to add to the operational section of the Kafka
documentation.
On Feb 5, 2014, at 2:18 PM, Andrew Otto wrote:
>> - Increasing num.replica.fetchers (defaults is one)
> Awesome! I just tried this one, bumped it up to 8 (12 cores on this broker
> box). It is now catching up a
> - Increasing num.replica.fetchers (defaults is one)
Awesome! I just tried this one, bumped it up to 8 (12 cores on this broker
box). It is now catching up at around 17K msgs/sec, which will mean it will
finish in about 4 or 5 hours. I’ll check up on it again tomorrow.
That should do it, Th
> topics are all caught up, but I have one high volume topic (around
> 40K msgs/sec) that is taking much longer. I just took a few samples
> of Replica-MaxLag to see how long it would take to catch up.
> Currently, it is behind about 12.5 million messages and is catching
> up at a rate of about 1
Hi all!
I recently had a problem where one out of two of my brokers would not reboot
due to a hardware failure. The broker was down for almost a week before the
required part came in and was fixed by our datacenter tech. During that time,
the live broker was able to handle all messages for al
