[
https://issues.apache.org/jira/browse/KAFKA-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329675#comment-14329675
]
Jun Rao commented on KAFKA-1971:
--------------------------------
[~gwenshap], what you said only applies to the case when you hard kill the
broker. However, if you hard kill the broker, you may not hit the
de-registration code anyway.
> 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
> Fix For: 0.8.3
>
>
> 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)