[CURATOR-360] Allow Zookeeper servers in TestingCluster to listen on network interfaces other than localhost - ASF JIRA

Voters

Watch issue

Watchers

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Closed
Priority: Minor
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 3.3.0, 2.12.0
Component/s: Tests
Labels:
- test-framework

Description

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.

Attachments

Issue Links

Add Link

links to

GitHub Pull Request #175

Delete this link

Activity

Comment

This comment will be Viewable by All Users Viewable by All Users

Cancel

People

Assignee:: Unassigned

Reporter:: Imesha Sudasingha

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 29/Nov/16 23:47

Updated:: 05/Dec/16 05:09

Resolved:: 05/Dec/16 02:09

Agile

View on Board

Allow Zookeeper servers in TestingCluster to listen on network interfaces other than localhost