Patrick Hunt updated ZOOKEEPER-635:

    Attachment: ZOOKEEPER-635.patch

this patch is the same as the last except:

1) removed the clientportbindhostname and move to just using the bind address
2) added a new test (be sure to svn add it) that verifies binding to a specific 

3) my machine has ipv6 addr for the lo, which the test uses. this was failing. 
I needed to fix the ZooKeeper client to allow ipv6 addresses (see 
ZOOKEEPER-667). Currently the ipv6 connect string is specified as ipv6:port 
where we look for the last :# and use that as the port. this should work fine 
but it means that the user must always specify ipv6:port, whereas for ipv4 you 
can just specify the ipv4address and the port will default to 2181, see 667 for 
more details on this.

> Server supports listening on a specified network address
> --------------------------------------------------------
>                 Key: ZOOKEEPER-635
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-635
>             Project: Zookeeper
>          Issue Type: New Feature
>          Components: server
>    Affects Versions: 3.2.1
>            Reporter: Steve Chu
>            Assignee: Patrick Hunt
>             Fix For: 3.3.0
>         Attachments: ZOOKEEPER-635.patch, ZOOKEEPER-635.patch, 
> ZOOKEEPER-635.patch
> The issue in maililist is located:
> http://mail-archives.apache.org/mod_mbox/hadoop-zookeeper-user/200912.mbox/%3c4ac0d28c0912210242g58230a9ds1c55361561c70...@mail.gmail.com%3e
> I have checked the server size code, seems no this option provided. This 
> feature is useful when we have more than two network interfaces, one for 
> Internet and others for intranet. We want to run ZooKeeper in our intranet 
> and not be exposed  to outside world.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to