Subject: Re: Controller is not being failed over 0.8.1
The following suggest that the controlled shutdown failed. Since you are
many partitions, you probably need to increase
controlled.shutdown.retry.backoff.ms and controlled.shutdown.max.retries to
give enough time for the controlled shutdown to
hannels.Channels$ReadableByteChannelImpl.read(Channels.java:387)
> at kafka.utils.Utils$.read(Utils.scala:375)
> at
> kafka.network.BoundedByteBufferReceive.readFrom(BoundedByteBufferReceive.scala:54)
> at
> kafka.network.Receive$class.readCompletely(Transmission.scala:56)
>
ntrollerEpochListener on 1]: Initialized
controller epoch to 3 and zk version 2
(kafka.controller.ControllerEpochListener)
[2014-04-17 09:20:09.904-0600] INFO [Controller 1]: Controller starting up
(kafka.controller.KafkaController)
[2014-04-17 09:20:09.961-0600] INFO [Controller 1]: Controller startup
: Controller is not being failed over 0.8.1
What's the controller value in the zk path (see
https://cwiki.apache.org/confluence/display/KAFKA/Kafka+data+structures+in+Zookeeper)?
Any error in the controller/state-change log?
Thanks,
Jun
On Wed, Apr 16, 2014 at 10:07 AM, Seshadri, Balaji wrote:
What's the controller value in the zk path (see
https://cwiki.apache.org/confluence/display/KAFKA/Kafka+data+structures+in+Zookeeper)?
Any error in the controller/state-change log?
Thanks,
Jun
On Wed, Apr 16, 2014 at 10:07 AM, Seshadri, Balaji wrote:
> Hi,
>
> We got the following error spamm
Hi,
We got the following error spamming the logs when broker 1 is the controller
and we are shutting it down in controlled manner not kill -9.
The leader being switched to broker 2 for all partitions but controller is not
being failed over to broker 2.
[2014-04-16 10:48:47.976-0600] ERROR [Con
