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

Posted to dev@zookeeper.apache.org by "Marshall McMullen (JIRA)" <ji...@apache.org> on 2013/05/31 19:22:20 UTC

[jira] [Commented] (ZOOKEEPER-1711) ZooKeeper server binds to all ip addresses for leader election and broadcast

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

Marshall McMullen commented on ZOOKEEPER-1711:
----------------------------------------------

Is this the same as: https://issues.apache.org/jira/browse/ZOOKEEPER-1096 ??
                
> ZooKeeper server binds to all ip addresses for leader election and broadcast
> ----------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1711
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1711
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.4.5
>         Environment: Any
>            Reporter: Germán Blanco
>            Priority: Minor
>             Fix For: 3.4.6
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Unlike current ZooKeeper version in trunk intended for release as 3.5.0, the current ZooKeeper server version 3.4.5 binds to all ip addresses on the specified port for election. It only makes sense to bind to the ip address indicated in the configuration file, which is where the other servers will connect. Listening to other ip addresses could have bad security implications.

--
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