[jira] [Created] (GEODE-4129) gfsh list members command feels inconsistent

["Jens Deppe (JIRA)" <ji...@apache.org>]

Jens Deppe created GEODE-4129:
---------------------------------

             Summary: gfsh list members command feels inconsistent
                 Key: GEODE-4129
                 URL: https://issues.apache.org/jira/browse/GEODE-4129
             Project: Geode
          Issue Type: Bug
          Components: gfsh
            Reporter: Jens Deppe


{{list members}} now also shows the 'coordinator':
{noformat}
gfsh>list members
    Name     | Id
------------ | ------------------------------------------------
Coordinator: | 10.118.19.26(locator1:7903:locator)<ec><v0>:1024
locator1     | 10.118.19.26(locator1:7903:locator)<ec><v0>:1024
server1      | 10.118.19.26(server1:7933)<v1>:1025
server2      | 10.118.19.26(server2:8075)<v2>:1026
{noformat}

This just looks untidy.

Here {{server-2}} is part of a group:

{noformat}
gfsh>list members --group=group1
    Name     | Id
------------ | ------------------------------------------------
Coordinator: | 10.118.19.26(locator1:7903:locator)<ec><v0>:1024
server2      | 10.118.19.26(server2:8075)<v2>:1026
{noformat}

But the 'coordinator' is not part of that group. Again, inconsistent and untidy.

I would prefer the relevant member to be highlight somehow as a coordinator. For example:

{noformat}
gfsh>list members
    Name     | Id
------------ | ------------------------------------------------
locator1     | 10.118.19.26(locator1:7903:locator)<ec><v0>:1024 [coordinator]
server1      | 10.118.19.26(server1:7933)<v1>:1025
server2      | 10.118.19.26(server2:8075)<v2>:1026
{noformat}

Or perhaps better yet would be to introduce a separate {{list coordinator}} command.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)