[jira] [Commented] (KAFKA-1600) Controller failover not working correctly.

["Guozhang Wang (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102419#comment-14102419 ] 

Guozhang Wang commented on KAFKA-1600:
--------------------------------------

Hello Haifeng,

Could you upload the broker and controller log of broker A here?

> Controller failover not working correctly.
> ------------------------------------------
>
>                 Key: KAFKA-1600
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1600
>             Project: Kafka
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 0.8.1
>         Environment: Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64 GNU/Linux
> java version "1.7.0_03"
>            Reporter: Ding Haifeng
>            Assignee: Neha Narkhede
>
> We are running a 10 node Kafka 0.8.1 cluster and experienced a failure as following. 
> At some time, broker A stopped acting as controller any more. We see this by kafka.controller - KafkaController - ActiveControllerCount in JMX metrics jumped from 1 to 0.
> In the meanwhile, broker A was still running and registering itself in the zookeeper /kafka/controller node. So no other brokers could be elected as new controller.
> Since that the cluster was running without controller. Producers and consumers still worked. But functions requiring a controller such as new topic leader election and topic leader failover were not working any more.
> A force restart of broker A could lead to a controller election and bring the cluster back to a correct state.
> Here is our brief observations. I can provide more necessary informations if needed.



--
This message was sent by Atlassian JIRA
(v6.2#6252)