[
https://issues.apache.org/jira/browse/KAFKA-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332414#comment-14332414
]
Guozhang Wang commented on KAFKA-1971:
--------------------------------------
I think that is because when the controller node is shutting down while there
are still in-flight requests to itself in the request channel, the shutdown
process will be blocked upon waiting for controller model to drain all the
requests. Deleting the ZK path will allow the controller listener to fire and
clear the corresponding request channel and resolve the dead-lock.
> starting a broker with a conflicting id will delete the previous broker
> registration
> ------------------------------------------------------------------------------------
>
> Key: KAFKA-1971
> URL: https://issues.apache.org/jira/browse/KAFKA-1971
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.2.0
> Reporter: Jun Rao
> Assignee: Jun Rao
> Priority: Blocker
> Fix For: 0.8.2.1
>
>
> This issue can be easily reproduced by the following steps.
> 1. Start broker 1.
> 2. Start broker 2 with the same id as broker 1 (configure different port, log
> dir).
> Broker 2's registration will fail. However, broker 1's registration in ZK is
> now deleted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
