[
https://issues.apache.org/jira/browse/GEODE-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16332755#comment-16332755
]
ASF GitHub Bot commented on GEODE-4061:
---------------------------------------
karensmolermiller closed pull request #1309: GEODE-4061 Update docs output for
gfsh list members;
URL: https://github.com/apache/geode/pull/1309
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb
b/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb
index 36c2ccfdbc..9b53d13b58 100644
--- a/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb
+++ b/geode-docs/getting_started/15_minute_quickstart_gfsh.html.md.erb
@@ -127,10 +127,11 @@ In this step you create a region with the `gfsh` command
line utility. Regions a
``` pre
gfsh>list members
- Name | Id
- -------- | ---------------------------------------
- locator1 | 192.0.2.0(locator1:3529:locator)<v0>:59926
- server1 | 192.0.2.0(server1:3883)<v1>:65390
+ Name | Id
+ ------------ | ---------------------------------------
+ Coordinator: | 192.0.2.0(locator1:3529:locator)<ec><v0>:59926
+ locator1 | 192.0.2.0(locator1:3529:locator)<ec><v0>:59926
+ server1 | 192.0.2.0(server1:3883)<v1>:65390
```
4. To view specifics about a region, type the following:
@@ -425,11 +426,12 @@ In this step you restart the cache servers in parallel.
Because the data is pers
``` pre
gfsh>list members
- Name | Id
- -------- | ---------------------------------------
- server2 | ubuntu(server2:3992)<v8>:21507
- server1 | ubuntu(server1:3402)<v7>:36532
- locator1 | ubuntu(locator1:2813:locator)<v0>:46644
+ Name | Id
+ ------------ | ---------------------------------------
+ Coordinator: | ubuntu(locator1:2813:locator)<ec><v0>:46644
+ locator1 | ubuntu(locator1:2813:locator)<ec><v0>:46644
+ server2 | ubuntu(server2:3992)<v8>:21507
+ server1 | ubuntu(server1:3402)<v7>:36532
```
6. Run a query to verify that all the data you entered with the `put`
commands is available:
diff --git a/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb
b/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb
index fd4f05797e..bb09a2ca32 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb
@@ -445,6 +445,12 @@ personIndex | /Person | [name, email, address,
revenue]
Display all or a subset of members.
+Within the output, the membership coordinator is listed.
+`<vN>` identifies which view the member currently has;
+`N` will be zero or a positive integer.
+`<ec>` indicates which members are eligible to be a membership
+coordinator.
+
**Availability:** Online. You must be connected in `gfsh` to a JMX Manager
member to use this command.
**Syntax:**
@@ -471,11 +477,12 @@ list members --group=Group1
``` pre
gfsh>list members
- Name | Id
--------- | -------------------------------------
-server1 | 192.0.2.0(server1:888)<v7>:10839
-server2 | 192.0.2.0(server2:3260)<v8>:16721
-locator1 | 192.0.2.0(locator1:216:locator):33368
+ Name | Id
+------------ | -------------------------------------
+Coordinator: | 192.0.2.0(locator1:216:locator)<ec><v6>:33368
+locator1 | 192.0.2.0(locator1:216:locator)<ec><v6>:33368
+server1 | 192.0.2.0(server1:888)<v7>:10839
+server2 | 192.0.2.0(server2:3260)<v8>:16721
```
## <a id="topic_F0ECEFF26086474498598035DD83C588"
class="no-quick-link"></a>list regions
diff --git a/geode-docs/tools_modules/gfsh/tour_of_gfsh.html.md.erb
b/geode-docs/tools_modules/gfsh/tour_of_gfsh.html.md.erb
index 9ae206e5f3..454adb65c1 100644
--- a/geode-docs/tools_modules/gfsh/tour_of_gfsh.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/tour_of_gfsh.html.md.erb
@@ -207,10 +207,11 @@ log files.
``` pre
gfsh>list members
- Name | Id
--------- | ---------------------------------------
-locator1 | ubuntu(locator1:5610:locator)<v0>:34168
-server1 | ubuntu(server1:5931)<v1>:35285
+ Name | Id
+------------ | ---------------------------------------
+Coordinator: | ubuntu(locator1:5610:locator)<ec><v0>:34168
+locator1 | ubuntu(locator1:5610:locator)<ec><v0>:34168
+server1 | ubuntu(server1:5931)<v1>:35285
```
**Step 8: View member details by executing the `describe member` command.**
----------------------------------------------------------------
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]
> Adding coordinator in list member command output
> ------------------------------------------------
>
> Key: GEODE-4061
> URL: https://issues.apache.org/jira/browse/GEODE-4061
> Project: Geode
> Issue Type: Bug
> Components: docs, gfsh, messaging
> Reporter: dinesh ak
> Assignee: Karen Smoler Miller
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.4.0
>
>
> no way to find out the coordinator apart from log messages.
> i have added coordinator in list member command output.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
