[ https://issues.apache.org/jira/browse/KAFKA-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711498#comment-14711498 ]
ASF GitHub Bot commented on KAFKA-1811: --------------------------------------- GitHub user eribeiro opened a pull request: https://github.com/apache/kafka/pull/168 KAFKA-1811 Ensuring registered broker host:port is unique Adds a ZKLock recipe implementation to guarantee that the host:port pair is unique among the brokers registered on ZooKeeper. You can merge this pull request into a Git repository by running: $ git pull https://github.com/eribeiro/kafka KAFKA-1811 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/168.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #168 ---- commit a9941892833e8e25c36ee0aac8704143863db452 Author: Edward Ribeiro <edward.ribe...@gmail.com> Date: 2015-08-25T15:29:12Z KAFKA-1811 Ensuring registered broker 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 > Assignee: Edward Ribeiro > Labels: newbie > Attachments: KAFKA-1811.patch, 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)