[
https://issues.apache.org/jira/browse/GEODE-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16331427#comment-16331427
]
ASF GitHub Bot commented on GEODE-4129:
---------------------------------------
jinmeiliao opened a new pull request #1308: GEODE-4129: do not list coordinator
as a different entry in list memb…
URL: https://github.com/apache/geode/pull/1308
…er command
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced in
the commit message?
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically `develop`)?
- [ ] Is your initial contribution a single, squashed commit?
- [ ] Does `gradlew build` run cleanly?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and
submit an update to your PR as soon as possible. If you need help, please
send an
email to [email protected].
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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
> Priority: Major
> Labels: pull-request-available
>
> {{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
(v7.6.3#76005)
