[
https://issues.apache.org/jira/browse/KAFKA-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244220#comment-14244220
]
Gwen Shapira commented on KAFKA-1811:
-------------------------------------
#3 - I think the main issue here is with the ZK registration. If the
SocketServer fails to start, there will be no registration and therefore no
uniqueness issue. Perhaps [~junrao] can confirm.
#4 - Perhaps check how we maintain broker ID uniqueness? I think that just
creating a znode in ZK with the id as the name will force ZK to guarantee
uniqueness for us (by failing to write if the znode exists), but perhaps there
is more involved. Anyway, may be a good place to start.
[~nehanarkhede] may have better suggestions here.
> 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)
