You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Jiangjie Qin (JIRA)" <ji...@apache.org> on 2015/09/03 01:41:45 UTC

[jira] [Updated] (KAFKA-2437) Controller did not handle zk node deletion correctly.

     [ https://issues.apache.org/jira/browse/KAFKA-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jiangjie Qin updated KAFKA-2437:
--------------------------------
    Summary: Controller did not handle zk node deletion correctly.  (was: Controller lost /controller zookeeper watcher.)

> Controller did not handle zk node deletion correctly.
> -----------------------------------------------------
>
>                 Key: KAFKA-2437
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2437
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jiangjie Qin
>            Assignee: Jiangjie Qin
>
> We see this issue occasionally. The symptom is that when /controller path got deleted, the old controller does not resign so we end up having more than one controller in the cluster (although the requests from controller with old epoch will not be accepted). After checking zookeeper watcher by using wchp, it looks the zookeeper session who created the /controller path does not have a watcher on /controller. That causes the old controller not resigning. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)