[
https://issues.apache.org/jira/browse/KAFKA-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-675:
----------------------------
Attachment: KAFKA-675-v3.patch
Here is a slightly tweaked version of your patch. I just fixed some problems in
the error messages in socket server--i.e. if you give a bad hostname or port
you don't have permission on it should fail with a clear message. If not
objections I will checkin this patch.
> Only bind to the interface declared in the 'hostname' config property
> ---------------------------------------------------------------------
>
> Key: KAFKA-675
> URL: https://issues.apache.org/jira/browse/KAFKA-675
> Project: Kafka
> Issue Type: Improvement
> Components: config, core
> Affects Versions: 0.8
> Reporter: Matan
> Priority: Minor
> Attachments: kafka-675.patch, kafka-675-updated.patch,
> KAFKA-675-v3.patch
>
>
> At the moment, Kafka always binds to all interfaces (0.0.0.0) which isn't
> ideal on some environments, even if the 'hostname' config parameter is set.
> Kafka should only bind to the interface set in the 'hostname' parameter -
> which defaults to InetAddress.getLocalHost.getHostAddress
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
