You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Neha Narkhede (JIRA)" <ji...@apache.org> on 2013/01/24 06:35:12 UTC

[jira] [Closed] (KAFKA-675) Only bind to the interface declared in the 'hostname' config property

     [ https://issues.apache.org/jira/browse/KAFKA-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Neha Narkhede closed KAFKA-675.
-------------------------------

    
> 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
>            Assignee: Jay Kreps
>            Priority: Minor
>             Fix For: 0.8
>
>         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