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

Posted to dev@curator.apache.org by "Cameron McKenzie (JIRA)" <ji...@apache.org> on 2016/12/05 02:09:58 UTC

[jira] [Resolved] (CURATOR-360) Allow Zookeeper servers in TestingCluster to listen on network interfaces other than localhost

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

Cameron McKenzie resolved CURATOR-360.
--------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.11.2
                   3.2.2

> 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
>             Fix For: 3.2.2, 2.11.2
>
>
> 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)