GFSH connect does not support using multiple locators in the connection string

Products

• VMware Tanzu Gemfire

Issue/Introduction

When you running the GFSH command, connect --locator, you receive a Connection refused exception if the first locator is down.

Localhost[7800] is down and localhost[7801] is running in the example below:

gfsh>connect --locator=localhost[7800],localhost[7801]
Connecting to Locator at [host=localhost, port=7800] ..
Connection refused (Connection refused)

gfsh>connect --locator=localhost[7801],localhost[7800]
Connecting to Locator at [host=localhost, port=7801] ..
Connecting to Manager at [host=192.168.3.2, port=1099] ..
Successfully connected to: [host=192.168.3.2, port=1099]
You are connected to a cluster of version: 9.10.5

Environment

Product Version: 9.1

Resolution

This is expected behavior. Unlike a normal client, the gfsh does not support multiple locators in its connection string and only the first entry is used.

Note: An internal ticket as been opened to have gfsh display an error message to tell the user that specifying multiple locators is not supported in future versions.