What is the best practice for doing so?
Thanks
Rob
On May 16, 2014, at 12:55 PM, Neha Narkhede wrote:
>>> Am I right with the above?
>
> That is the hacky way of deleting a topic and has not been well tested and
> hence is not certified to work. There are also several race conditions in
> the
Hi all, and thanks for a fantastic product.
The other day our kafka node in our test environment went down due to full
disc. I reconfigured kafka to save fewer messages, and restarted the node.
It is a single node setup. At restart the node freed up some disc space,
but no new messages where accep
What's the value of under replicated partitions JMX in each broker?
Thanks,
Jun
On Sat, May 17, 2014 at 6:16 PM, Paul Mackles wrote:
> Today we did a rolling restart of ZK. We also restarted the kafka
> controller and ISRs are still not being updated in ZK. Again, the cluster
> seems fine and
In this case, you had an unclean shutdown. So, on restart, the broker has
to do log recovery before it can be online. Not sure why you get the WARN
though. Which version of Kafka are you using?
Thanks,
Jun
On Sun, May 18, 2014 at 2:45 PM, Jonas Bergström wrote:
> Hi all, and thanks for a fanta
Do you see ZK session expiration in the log?
Thanks,
Jun
On Fri, May 16, 2014 at 8:06 PM, Mingmin Liu wrote:
> see these errors in producer's log:
>
>
> ＝＝＝
> [2014-05-17 08:38:59,983] ERROR Error handling event ZkEvent[Children of
> /brokers/topics/test_device_updates changed sent to kafka
>
Perhaps you will have to lower the tcp alive interval to avoid the socket
connection from being killed.
Thanks,
Jun
On Fri, May 16, 2014 at 2:12 PM, Robin Yamaguchi wrote:
> The only errors logged are in the controller log:
>
> [2014-05-16 20:42:31,846] DEBUG [TopicChangeListener on Controller
