[
https://issues.apache.org/jira/browse/ZOOKEEPER-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831011#action_12831011
]
Patrick Hunt commented on ZOOKEEPER-635:
----------------------------------------
I wrote the docs first, then during impl noticed that the two funnel down to
the same code. I thought about it a bit
and convinced myself that having two variable made it more understandable to
the user, so I didn't change it from
my original approach. I could go either way though. What would you call it if
there's just one? clientPortBindAddress
and just spec in the docs that it's either ip addr or name?
Re the testing I was concerned that I could not get reproduceable tests if I
tried tying it to a particular interface. Do
you know (think of) a bulletproof approach? Something that will work in all
cases, incl ipv6 (esp where the hosts
file might cause problems)
> 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
>
>
> 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.
