[ 
https://issues.apache.org/jira/browse/KAFKA-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534439#comment-13534439
 ] 

Jay Kreps commented on KAFKA-675:
---------------------------------

Nice. So does the default make it bind to all hosts?

Guys--I recommend we take this for 0.8. Since we have a configuration for this 
it should work and without this I think kafka won't run well on AWS.
                
> 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

Reply via email to