[
https://issues.apache.org/jira/browse/KAFKA-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244603#comment-14244603
]
Neha Narkhede commented on KAFKA-1811:
--------------------------------------
As [~gwenshap] points out correctly, the issue is during the zookeeper
registration. While a broker checks for uniqueness, another broker could sneak
in and register itself. The correct way of doing this is a little complicated.
Basically, all brokers would have to register in a 2-step process - 1. Acquire
a lock (zk path) in order to register itself. 2. If the lock is successfully
acquired, proceed with registration if the host:port is unique.
> ensuring registered broker host:port is unique
> ----------------------------------------------
>
> Key: KAFKA-1811
> URL: https://issues.apache.org/jira/browse/KAFKA-1811
> Project: Kafka
> Issue Type: Improvement
> Reporter: Jun Rao
> Labels: newbie
> Attachments: KAFKA_1811.patch
>
>
> Currently, we expect each of the registered broker to have a unique host:port
> pair. However, we don't enforce that, which causes various weird problems. It
> would be useful to ensure this during broker registration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
