[
https://issues.apache.org/jira/browse/KAFKA-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534462#comment-13534462
]
Jay Kreps commented on KAFKA-675:
---------------------------------
I think I probably broke this without realizing it so I can act as point of
contact for this.
I am not sure if I follow what you are saying, but I think the ideal would be:
1. By default we bind to all interfaces, but you can override if you want to
specify one
2. We always publish the host name for one of the interfaces we bound to
I think we probably should be defaulting the hostname to null which would
signal us to bind without a hostname and to register
InetAddress.getLocalHost.getHostAddress for others to connect to (or perhaps we
should be using getCanonicalHostName()?). But if you give us a config for the
hostname we just use that.
> 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
>
>
> 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
