[
https://issues.apache.org/jira/browse/CURATOR-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15720763#comment-15720763
]
ASF GitHub Bot commented on CURATOR-360:
----------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/curator/pull/175
> Allow Zookeeper servers in TestingCluster to listen on network interfaces
> other than localhost
> ----------------------------------------------------------------------------------------------
>
> Key: CURATOR-360
> URL: https://issues.apache.org/jira/browse/CURATOR-360
> Project: Apache Curator
> Issue Type: Improvement
> Components: Tests
> Reporter: Imesha Sudasingha
> Priority: Minor
> Labels: test-framework
>
> Currently, when we create a TestingCluster, all the TestingServers will be
> bound to the local interface (127.0.0.1). This becomes a constraint if we
> want to run a TestingCluster which can be used for testing over a network
> (say LAN).
> In order to address that we can add a hostname to be provided optionally in
> the InstanceSpec.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
