You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Bruce Schuchardt (JIRA)" <ji...@apache.org> on 2019/05/14 17:09:00 UTC
[jira] [Created] (GEODE-6769) gfsh doesn't always note which node
is the coordinator in "list members"
Bruce Schuchardt created GEODE-6769:
---------------------------------------
Summary: gfsh doesn't always note which node is the coordinator in "list members"
Key: GEODE-6769
URL: https://issues.apache.org/jira/browse/GEODE-6769
Project: Geode
Issue Type: Bug
Components: gfsh
Reporter: Bruce Schuchardt
Gfsh doesn't always note which member is the coordinator of the cluster. Here is output from two concurrently starting locators and two concurrently starting servers:
{noformat}
(1) Executing - connect --locator=localhost[24589]
Connecting to Locator at [host=localhost, port=24589] ..
Connecting to Manager at [host=10.118.20.62, port=24590] ..
Successfully connected to: [host=10.118.20.62, port=24590]
(2) Executing - list members
Name | Id
--------- | ---------------------------------------------------
locator-2 | 10.118.20.62(locator-2:13557:locator)<ec><v0>:41000
server-1 | 10.118.20.62(server-1:13558)<v2>:41001
locator-1 | 10.118.20.62(locator-1:13559:locator)<ec><v1>:41002
server-2 | 10.118.20.62(server-2:13560)<v1>:41003
(1) Executing - connect --locator=localhost[24591]
Connecting to Locator at [host=localhost, port=24591] ..
Connecting to Manager at [host=10.118.20.62, port=24592] ..
Successfully connected to: [host=10.118.20.62, port=24592]
(2) Executing - list members
Name | Id
--------- | -----------------------------------------------------------------
locator-2 | 10.118.20.62(locator-2:13557:locator)<ec><v0>:41000 [Coordinator]
server-1 | 10.118.20.62(server-1:13558)<v2>:41001
locator-1 | 10.118.20.62(locator-1:13559:locator)<ec><v1>:41002
server-2 | 10.118.20.62(server-2:13560)<v1>:41003
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)