well. I just run the kafka-run-class.sh script with DeleteTopicCommand
class directly.
I noticed the warning on documentation http://DeleteTopicCommand page.
but I thought it is only about not complete cleanup. I didn't know it can
affect cluster health. maybe it's worthwhile to point it out the
yes. I deleted a topic. but not at the time. it's a few hours before.
On Fri, May 16, 2014 at 3:49 PM, Jun Rao jun...@gmail.com wrote:
The problem is indicated by the following log in broker 1's controller log.
Were you deleting any topic at that time?
[2014-05-12 21:24:37,930] ERROR
Delete topic is not supported in 0.8.1.1. How did you do it?
Thanks,
Jun
On Thu, May 22, 2014 at 9:59 AM, Steven Wu steve...@netflix.com wrote:
yes. I deleted a topic. but not at the time. it's a few hours before.
On Fri, May 16, 2014 at 3:49 PM, Jun Rao jun...@gmail.com wrote:
The
The problem is indicated by the following log in broker 1's controller log.
Were you deleting any topic at that time?
[2014-05-12 21:24:37,930] ERROR [BrokerChangeListener on Controller 1]:
Error while handling broker changes
(kafka.controller.ReplicaStateMachine$BrokerChangeListener)
The controller log in broker 1 is too late. Could you send its log
around 2014-05-12 21:24:37?
Thanks,
Jun
On Mon, May 12, 2014 at 5:02 PM, Steven Wu steve...@netflix.com wrote:
This is a three-node cluster. broker 0 lost connection to ZK. broker 1
does seem to take the controller role. but
