curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Imesha Sudasingha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-360) Allow Zookeeper servers in TestingCluster to listen on network interfaces other than localhost
Date Mon, 05 Dec 2016 05:09:58 GMT

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

Imesha Sudasingha commented on CURATOR-360:
-------------------------------------------

You are welcome!

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

Mime
View raw message