[
https://issues.apache.org/jira/browse/KAFKA-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333015#comment-14333015
]
Jun Rao commented on KAFKA-1971:
--------------------------------
It seems that the reason why we explicitly delete the broker registration path
in ZK is to avoid the deadlock in shutting down the controller, because the
controller message queue is finite. We have since made the controller message
queue unbounded. So, we don't need to explicitly deregister the broker any
more.
Attached is a new patch.
> 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
>
> Attachments: kafka-1971_2015-02-22_21:11:52.patch
>
>
> 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)
