[jira] [Resolved] (GEODE-8916) The gfsh export stack traces command should include the locators

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-8916.

Fix Version/s: 1.14.0
   Resolution: Fixed

> The gfsh export stack traces command should include the locators
> 
>
> Key: GEODE-8916
> URL: https://issues.apache.org/jira/browse/GEODE-8916
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Barrett Oglesby
>Assignee: Barrett Oglesby
>Priority: Major
>  Labels: blocks-1.14.0​, pull-request-available
> Fix For: 1.14.0
>
>
> The gfsh export stack traces command should include the locators, but only 
> includes the servers.
> Here is an excerpt from a slack conversation showing the behavior:
> {noformat}
> Shelley Hughes-Godfrey  6:48 PM
> I have a question about gfsh export stack-traces ...
> "list members" shows me servers and locators ...
> gfsh>list members
> Member Count : 3
>   Name| Id
> - | 
> 
> gemfire-cluster-server-0  | xx.xx.x.xxx(gemfire-cluster-server-0:1):41000
> gemfire-cluster-locator-0 | 
> xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]
> gemfire-cluster-server-1  | xx.xx.x.xxx(gemfire-cluster-server-1:1):41000
> But, if I don't specify members on the export stack-traces command, I just 
> get the stacks for the servers.
> gfsh>export stack-traces
> stack-trace(s) exported to file: /path/stacktrace_1612316330340
> On host : ...
> Specifying a locator returns "No Members found"
> gfsh>export stack-traces --member=gemfire-cluster-locator-0
> No Members Found
> Also, it looks like copy-paste was done from export logs => export 
> stack-traces (for --members and --groups).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-8916) The gfsh export stack traces command should include the locators

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-8916:
--

Assignee: Barrett Oglesby

> The gfsh export stack traces command should include the locators
> 
>
> Key: GEODE-8916
> URL: https://issues.apache.org/jira/browse/GEODE-8916
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Barrett Oglesby
>Assignee: Barrett Oglesby
>Priority: Major
>  Labels: blocks-1.14.0​, pull-request-available
>
> The gfsh export stack traces command should include the locators, but only 
> includes the servers.
> Here is an excerpt from a slack conversation showing the behavior:
> {noformat}
> Shelley Hughes-Godfrey  6:48 PM
> I have a question about gfsh export stack-traces ...
> "list members" shows me servers and locators ...
> gfsh>list members
> Member Count : 3
>   Name| Id
> - | 
> 
> gemfire-cluster-server-0  | xx.xx.x.xxx(gemfire-cluster-server-0:1):41000
> gemfire-cluster-locator-0 | 
> xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]
> gemfire-cluster-server-1  | xx.xx.x.xxx(gemfire-cluster-server-1:1):41000
> But, if I don't specify members on the export stack-traces command, I just 
> get the stacks for the servers.
> gfsh>export stack-traces
> stack-trace(s) exported to file: /path/stacktrace_1612316330340
> On host : ...
> Specifying a locator returns "No Members found"
> gfsh>export stack-traces --member=gemfire-cluster-locator-0
> No Members Found
> Also, it looks like copy-paste was done from export logs => export 
> stack-traces (for --members and --groups).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-8917) Revise docs to match current gfsh export stack-traces behavior

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-8917.

Fix Version/s: 1.14.0
   Resolution: Fixed

> Revise docs to match current gfsh export stack-traces behavior
> --
>
> Key: GEODE-8917
> URL: https://issues.apache.org/jira/browse/GEODE-8917
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.14.0
>
>
> Our docs for gfsh export stack-traces do not match the current behavior. 
> Update the docs.
> If we don't specify members on the export stack-traces command, we only get 
> the traces for the servers.
> gfsh>export stack-traces
>  stack-trace(s) exported to file: /data/stacktrace_1612316330340
>  On host : 
> gemfire-cluster-locator-0.gemfire-cluster-locator.gemfire-system.svc.cluster.local
> gfsh>export stack-traces
> stack-trace(s) exported to file: /path/stacktrace_1612316330340
> On host : ...
> Specifying a locator returns "No Members found"
> gfsh>export stack-traces --member=gemfire-cluster-locator-0
> No Members Found
> Also, it looks like copy-paste was done from export logs => export 
> stack-traces (for --members and --groups).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-8917) Revise docs to match current gfsh export stack-traces behavior

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller updated GEODE-8917:
---
Description: 
Our docs for gfsh export stack-traces do not match the current behavior. Update 
the docs.

If we don't specify members on the export stack-traces command, we only get the 
traces for the servers.

gfsh>export stack-traces
 stack-trace(s) exported to file: /data/stacktrace_1612316330340
 On host : 
gemfire-cluster-locator-0.gemfire-cluster-locator.gemfire-system.svc.cluster.local

gfsh>export stack-traces
stack-trace(s) exported to file: /path/stacktrace_1612316330340
On host : ...

Specifying a locator returns "No Members found"

gfsh>export stack-traces --member=gemfire-cluster-locator-0
No Members Found

Also, it looks like copy-paste was done from export logs => export stack-traces 
(for --members and --groups).

  was:
Our docs for gfsh export stack-traces do not match the current behavior. Update 
the docs.

If we don't specify members on the export stack-traces command, we only get the 
traces for the servers.

gfsh>export stack-traces
 stack-trace(s) exported to file: /data/stacktrace_1612316330340
 On host : 
gemfire-cluster-locator-0.gemfire-cluster-locator.gemfire-system.svc.cluster.local

gfsh>export stack-traces
stack-trace(s) exported to file: /path/stacktrace_1612316330340
On host : ...

Specifying a locator returns "No Members found"

{{gfsh>export stack-traces --member=gemfire-cluster-locator-0}}
No Members Found

Also, it looks like copy-paste was done from export logs => export stack-traces 
(for --members and --groups).


> Revise docs to match current gfsh export stack-traces behavior
> --
>
> Key: GEODE-8917
> URL: https://issues.apache.org/jira/browse/GEODE-8917
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> Our docs for gfsh export stack-traces do not match the current behavior. 
> Update the docs.
> If we don't specify members on the export stack-traces command, we only get 
> the traces for the servers.
> gfsh>export stack-traces
>  stack-trace(s) exported to file: /data/stacktrace_1612316330340
>  On host : 
> gemfire-cluster-locator-0.gemfire-cluster-locator.gemfire-system.svc.cluster.local
> gfsh>export stack-traces
> stack-trace(s) exported to file: /path/stacktrace_1612316330340
> On host : ...
> Specifying a locator returns "No Members found"
> gfsh>export stack-traces --member=gemfire-cluster-locator-0
> No Members Found
> Also, it looks like copy-paste was done from export logs => export 
> stack-traces (for --members and --groups).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-8917) Revise docs to match current gfsh export stack-traces behavior

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller updated GEODE-8917:
---
Description: 
Our docs for gfsh export stack-traces do not match the current behavior. Update 
the docs.

If we don't specify members on the export stack-traces command, we only get the 
traces for the servers.

gfsh>export stack-traces
 stack-trace(s) exported to file: /data/stacktrace_1612316330340
 On host : 
gemfire-cluster-locator-0.gemfire-cluster-locator.gemfire-system.svc.cluster.local

gfsh>export stack-traces
stack-trace(s) exported to file: /path/stacktrace_1612316330340
On host : ...

Specifying a locator returns "No Members found"

{{gfsh>export stack-traces --member=gemfire-cluster-locator-0}}
No Members Found

Also, it looks like copy-paste was done from export logs => export stack-traces 
(for --members and --groups).

  was:
Our docs for gfsh export stack-traces do not match the current behavior. Update 
the docs.

Shelley Hughes-Godfrey: I have a question about gfsh export stack-traces ... 
"list members" shows me servers and locators ...
 gfsh>list members
 Member Count : 3 Name | Id
 - | 

 gemfire-cluster-server-0 | 10.40.4.192(gemfire-cluster-server-0:1):41000
 gemfire-cluster-locator-0 | 
10.40.5.147(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]
 gemfire-cluster-server-1 | 10.40.7.129(gemfire-cluster-server-1:1):41000

{{But, if I don't specify members on the export stack-traces command, I just 
get the stacks for the servers.}}

gfsh>export stack-traces
 stack-trace(s) exported to file: /data/stacktrace_1612316330340
 On host : 
gemfire-cluster-locator-0.gemfire-cluster-locator.gemfire-system.svc.cluster.local

{{gfsh>export stack-traces}}
 \{{ stack-trace(s) exported to file: /path/stacktrace_1612316330340}}
 \{{ On host : ...}}{{Specifying a locator returns "No Members 
found"}}{{gfsh>export stack-traces --member=gemfire-cluster-locator-0}}
 \{{ No Members Found}}

Also, it looks like copy-paste was done from export logs => export stack-traces 
(for --members and --groups).


> Revise docs to match current gfsh export stack-traces behavior
> --
>
> Key: GEODE-8917
> URL: https://issues.apache.org/jira/browse/GEODE-8917
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> Our docs for gfsh export stack-traces do not match the current behavior. 
> Update the docs.
> If we don't specify members on the export stack-traces command, we only get 
> the traces for the servers.
> gfsh>export stack-traces
>  stack-trace(s) exported to file: /data/stacktrace_1612316330340
>  On host : 
> gemfire-cluster-locator-0.gemfire-cluster-locator.gemfire-system.svc.cluster.local
> gfsh>export stack-traces
> stack-trace(s) exported to file: /path/stacktrace_1612316330340
> On host : ...
> Specifying a locator returns "No Members found"
> {{gfsh>export stack-traces --member=gemfire-cluster-locator-0}}
> No Members Found
> Also, it looks like copy-paste was done from export logs => export 
> stack-traces (for --members and --groups).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-8917) Revise docs to match current gfsh export stack-traces behavior

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller updated GEODE-8917:
---
Description: 
Our docs for gfsh export stack-traces do not match the current behavior. Update 
the docs.

Shelley Hughes-Godfrey: I have a question about gfsh export stack-traces ... 
"list members" shows me servers and locators ...
 gfsh>list members
 Member Count : 3 Name | Id
 - | 

 gemfire-cluster-server-0 | 10.40.4.192(gemfire-cluster-server-0:1):41000
 gemfire-cluster-locator-0 | 
10.40.5.147(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]
 gemfire-cluster-server-1 | 10.40.7.129(gemfire-cluster-server-1:1):41000

{{But, if I don't specify members on the export stack-traces command, I just 
get the stacks for the servers.}}

gfsh>export stack-traces
 stack-trace(s) exported to file: /data/stacktrace_1612316330340
 On host : 
gemfire-cluster-locator-0.gemfire-cluster-locator.gemfire-system.svc.cluster.local

{{gfsh>export stack-traces}}
 \{{ stack-trace(s) exported to file: /path/stacktrace_1612316330340}}
 \{{ On host : ...}}{{Specifying a locator returns "No Members 
found"}}{{gfsh>export stack-traces --member=gemfire-cluster-locator-0}}
 \{{ No Members Found}}

Also, it looks like copy-paste was done from export logs => export stack-traces 
(for --members and --groups).

  was:
Our docs for gfsh export stack-traces do not match the current behavior. Update 
the docs.

Shelley Hughes-Godfrey: I have a question about gfsh export stack-traces ... 
"list members" shows me servers and locators ...
gfsh>list members
Member Count : 3  Name| Id
- | 

gemfire-cluster-server-0  | 10.40.4.192(gemfire-cluster-server-0:1):41000
gemfire-cluster-locator-0 | 
10.40.5.147(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]
gemfire-cluster-server-1  | 10.40.7.129(gemfire-cluster-server-1:1):41000
{{But, if I don't specify members on the export stack-traces command, I just 
get the stacks for the servers.}}
gfsh>export stack-traces
stack-trace(s) exported to file: /data/stacktrace_1612316330340
On host : 
gemfire-cluster-locator-0.gemfire-cluster-locator.gemfire-system.svc.cluster.local
{{gfsh>export stack-traces}}
 \{{ stack-trace(s) exported to file: /path/stacktrace_1612316330340}}
 \{{ On host : ...}}{{Specifying a locator returns "No Members 
found"}}{{gfsh>export stack-traces --member=gemfire-cluster-locator-0}}
 \{{ No Members Found}}

Also, it looks like copy-paste was done from export logs => export stack-traces 
(for --members and --groups).


> Revise docs to match current gfsh export stack-traces behavior
> --
>
> Key: GEODE-8917
> URL: https://issues.apache.org/jira/browse/GEODE-8917
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> Our docs for gfsh export stack-traces do not match the current behavior. 
> Update the docs.
> Shelley Hughes-Godfrey: I have a question about gfsh export stack-traces ... 
> "list members" shows me servers and locators ...
>  gfsh>list members
>  Member Count : 3 Name | Id
>  - | 
> 
>  gemfire-cluster-server-0 | 10.40.4.192(gemfire-cluster-server-0:1):41000
>  gemfire-cluster-locator-0 | 
> 10.40.5.147(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]
>  gemfire-cluster-server-1 | 10.40.7.129(gemfire-cluster-server-1:1):41000
> {{But, if I don't specify members on the export stack-traces command, I just 
> get the stacks for the servers.}}
> gfsh>export stack-traces
>  stack-trace(s) exported to file: /data/stacktrace_1612316330340
>  On host : 
> gemfire-cluster-locator-0.gemfire-cluster-locator.gemfire-system.svc.cluster.local
> {{gfsh>export stack-traces}}
>  \{{ stack-trace(s) exported to file: /path/stacktrace_1612316330340}}
>  \{{ On host : ...}}{{Specifying a locator returns "No Members 
> found"}}{{gfsh>export stack-traces --member=gemfire-cluster-locator-0}}
>  \{{ No Members Found}}
> Also, it looks like copy-paste was done from export logs => export 
> stack-traces (for --members and --groups).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-8917) Revise docs to match current gfsh export stack-traces behavior

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller updated GEODE-8917:
---
Description: 
Our docs for gfsh export stack-traces do not match the current behavior. Update 
the docs.

Shelley Hughes-Godfrey: I have a question about gfsh export stack-traces ... 
"list members" shows me servers and locators ...
gfsh>list members
Member Count : 3  Name| Id
- | 

gemfire-cluster-server-0  | 10.40.4.192(gemfire-cluster-server-0:1):41000
gemfire-cluster-locator-0 | 
10.40.5.147(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]
gemfire-cluster-server-1  | 10.40.7.129(gemfire-cluster-server-1:1):41000
{{But, if I don't specify members on the export stack-traces command, I just 
get the stacks for the servers.}}
gfsh>export stack-traces
stack-trace(s) exported to file: /data/stacktrace_1612316330340
On host : 
gemfire-cluster-locator-0.gemfire-cluster-locator.gemfire-system.svc.cluster.local
{{gfsh>export stack-traces}}
 \{{ stack-trace(s) exported to file: /path/stacktrace_1612316330340}}
 \{{ On host : ...}}{{Specifying a locator returns "No Members 
found"}}{{gfsh>export stack-traces --member=gemfire-cluster-locator-0}}
 \{{ No Members Found}}

Also, it looks like copy-paste was done from export logs => export stack-traces 
(for --members and --groups).

  was:
Our docs for gfsh export stack-traces do not match the current behavior. Update 
the docs.

Shelley Hughes-Godfrey: I have a question about gfsh export stack-traces ... 
"list members" shows me servers and locators ...

{{gfsh>list members}}
 \{{ Member Count : 3}}
 \{{ Name | Id}}
 \{{ - | 
}}
 \{{ gemfire-cluster-server-0 | 
xx.xx.x.xxx(gemfire-cluster-server-0:1):41000}}
 {{ gemfire-cluster-locator-0 | 
xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]}}
 \{{ gemfire-cluster-server-1 | 
xx.xx.x.xxx(gemfire-cluster-server-1:1):41000}}{{But, if I don't specify 
members on the export stack-traces command, I just get the stacks for the 
servers.}}{{gfsh>export stack-traces}}
 \{{ stack-trace(s) exported to file: /path/stacktrace_1612316330340}}
 \{{ On host : ...}}{{Specifying a locator returns "No Members 
found"}}{{gfsh>export stack-traces --member=gemfire-cluster-locator-0}}
 \{{ No Members Found}}

Also, it looks like copy-paste was done from export logs => export stack-traces 
(for --members and --groups).


> Revise docs to match current gfsh export stack-traces behavior
> --
>
> Key: GEODE-8917
> URL: https://issues.apache.org/jira/browse/GEODE-8917
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> Our docs for gfsh export stack-traces do not match the current behavior. 
> Update the docs.
> Shelley Hughes-Godfrey: I have a question about gfsh export stack-traces ... 
> "list members" shows me servers and locators ...
> gfsh>list members
> Member Count : 3  Name| Id
> - | 
> 
> gemfire-cluster-server-0  | 10.40.4.192(gemfire-cluster-server-0:1):41000
> gemfire-cluster-locator-0 | 
> 10.40.5.147(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]
> gemfire-cluster-server-1  | 10.40.7.129(gemfire-cluster-server-1:1):41000
> {{But, if I don't specify members on the export stack-traces command, I just 
> get the stacks for the servers.}}
> gfsh>export stack-traces
> stack-trace(s) exported to file: /data/stacktrace_1612316330340
> On host : 
> gemfire-cluster-locator-0.gemfire-cluster-locator.gemfire-system.svc.cluster.local
> {{gfsh>export stack-traces}}
>  \{{ stack-trace(s) exported to file: /path/stacktrace_1612316330340}}
>  \{{ On host : ...}}{{Specifying a locator returns "No Members 
> found"}}{{gfsh>export stack-traces --member=gemfire-cluster-locator-0}}
>  \{{ No Members Found}}
> Also, it looks like copy-paste was done from export logs => export 
> stack-traces (for --members and --groups).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-8917) Revise docs to match current gfsh export stack-traces behavior

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller updated GEODE-8917:
---
Description: 
Our docs for gfsh export stack-traces do not match the current behavior. Update 
the docs.

Shelley Hughes-Godfrey: I have a question about gfsh export stack-traces ... 
"list members" shows me servers and locators ...

{{gfsh>list members}}
 \{{ Member Count : 3}}
 \{{ Name | Id}}
 \{{ - | 
}}
 \{{ gemfire-cluster-server-0 | 
xx.xx.x.xxx(gemfire-cluster-server-0:1):41000}}
 {{ gemfire-cluster-locator-0 | 
xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]}}
 \{{ gemfire-cluster-server-1 | 
xx.xx.x.xxx(gemfire-cluster-server-1:1):41000}}{{But, if I don't specify 
members on the export stack-traces command, I just get the stacks for the 
servers.}}{{gfsh>export stack-traces}}
 \{{ stack-trace(s) exported to file: /path/stacktrace_1612316330340}}
 \{{ On host : ...}}{{Specifying a locator returns "No Members 
found"}}{{gfsh>export stack-traces --member=gemfire-cluster-locator-0}}
 \{{ No Members Found}}

Also, it looks like copy-paste was done from export logs => export stack-traces 
(for --members and --groups).

  was:
Our docs for gfsh export stack-traces do not match the current behavior. Update 
the docs.

{{Shelley Hughes-Godfrey 6:48 PM}}{{I have a question about gfsh export 
stack-traces ...}}{{"list members" shows me servers and locators 
...}}{{gfsh>list members}}
 \{{ Member Count : 3}}
 \{{ Name | Id}}
 \{{ - | 
}}
 \{{ gemfire-cluster-server-0 | 
xx.xx.x.xxx(gemfire-cluster-server-0:1):41000}}
 {{ gemfire-cluster-locator-0 | 
xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]}}
 \{{ gemfire-cluster-server-1 | 
xx.xx.x.xxx(gemfire-cluster-server-1:1):41000}}{{But, if I don't specify 
members on the export stack-traces command, I just get the stacks for the 
servers.}}{{gfsh>export stack-traces}}
 \{{ stack-trace(s) exported to file: /path/stacktrace_1612316330340}}
 \{{ On host : ...}}{{Specifying a locator returns "No Members 
found"}}{{gfsh>export stack-traces --member=gemfire-cluster-locator-0}}
 \{{ No Members Found}}

Also, it looks like copy-paste was done from export logs => export stack-traces 
(for --members and --groups).


> Revise docs to match current gfsh export stack-traces behavior
> --
>
> Key: GEODE-8917
> URL: https://issues.apache.org/jira/browse/GEODE-8917
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> Our docs for gfsh export stack-traces do not match the current behavior. 
> Update the docs.
> Shelley Hughes-Godfrey: I have a question about gfsh export stack-traces ... 
> "list members" shows me servers and locators ...
> {{gfsh>list members}}
>  \{{ Member Count : 3}}
>  \{{ Name | Id}}
>  \{{ - | 
> }}
>  \{{ gemfire-cluster-server-0 | 
> xx.xx.x.xxx(gemfire-cluster-server-0:1):41000}}
>  {{ gemfire-cluster-locator-0 | 
> xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]}}
>  \{{ gemfire-cluster-server-1 | 
> xx.xx.x.xxx(gemfire-cluster-server-1:1):41000}}{{But, if I don't specify 
> members on the export stack-traces command, I just get the stacks for the 
> servers.}}{{gfsh>export stack-traces}}
>  \{{ stack-trace(s) exported to file: /path/stacktrace_1612316330340}}
>  \{{ On host : ...}}{{Specifying a locator returns "No Members 
> found"}}{{gfsh>export stack-traces --member=gemfire-cluster-locator-0}}
>  \{{ No Members Found}}
> Also, it looks like copy-paste was done from export logs => export 
> stack-traces (for --members and --groups).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-8917) Revise docs to match current gfsh export stack-traces behavior

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller updated GEODE-8917:
---
Description: 
Our docs for gfsh export stack-traces do not match the current behavior. Update 
the docs.

{{Shelley Hughes-Godfrey 6:48 PM}}{{I have a question about gfsh export 
stack-traces ...}}{{"list members" shows me servers and locators 
...}}{{gfsh>list members}}
 \{{ Member Count : 3}}
 \{{ Name | Id}}
 \{{ - | 
}}
 \{{ gemfire-cluster-server-0 | 
xx.xx.x.xxx(gemfire-cluster-server-0:1):41000}}
 {{ gemfire-cluster-locator-0 | 
xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]}}
 \{{ gemfire-cluster-server-1 | 
xx.xx.x.xxx(gemfire-cluster-server-1:1):41000}}{{But, if I don't specify 
members on the export stack-traces command, I just get the stacks for the 
servers.}}{{gfsh>export stack-traces}}
 \{{ stack-trace(s) exported to file: /path/stacktrace_1612316330340}}
 \{{ On host : ...}}{{Specifying a locator returns "No Members 
found"}}{{gfsh>export stack-traces --member=gemfire-cluster-locator-0}}
 \{{ No Members Found}}

Also, it looks like copy-paste was done from export logs => export stack-traces 
(for --members and --groups).

  was:
Our docs for gfsh export stack-traces do not match the current behavior. Update 
the docs.

{{Shelley Hughes-Godfrey 6:48 PM}}{{I have a question about gfsh export 
stack-traces ...}}{{"list members" shows me servers and locators 
...}}{{gfsh>list members}}
{{ Member Count : 3}}
{{ Name | Id}}
{{ - | 
}}
{{ gemfire-cluster-server-0 | 
xx.xx.x.xxx(gemfire-cluster-server-0:1):41000}}
{{ gemfire-cluster-locator-0 | 
xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]}}
{{ gemfire-cluster-server-1 | 
xx.xx.x.xxx(gemfire-cluster-server-1:1):41000}}{{But, if I don't specify 
members on the export stack-traces command, I just get the stacks for the 
servers.}}{{gfsh>export stack-traces}}
{{ stack-trace(s) exported to file: /path/stacktrace_1612316330340}}
{{ On host : ...}}{{Specifying a locator returns "No Members 
found"}}{{gfsh>export stack-traces --member=gemfire-cluster-locator-0}}
{{ No Members Found}}{{Barry Oglesby 2 hours ago}}
{{ That command excludes the locators. It uses this method in ManagementUtils 
to get just the normal members:}}{{public static Set 
getAllNormalMembers(InternalCache cache) {}}
{{ return new HashSet(}}
{{ cache.getDistributionManager().getNormalDistributionManagerIds());}}
{{ }}}{{Shelley Hughes-Godfrey 1 hour ago}}{{So, I also ran "export logs" with 
--member=}}{{And that works}}{{gfsh>list members}}
{{ Member Count : 3}}
{{ Name | Id}}
{{ - | 
}}
{{ gemfire-cluster-server-0 | 
xx.xx.x.xxx(gemfire-cluster-server-0:1):41000}}
{{ gemfire-cluster-locator-0 | 
xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]}}
{{ gemfire-cluster-server-1 | 
xx.xx.x.xxx(gemfire-cluster-server-1:1):41000}}{{gfsh>export logs 
--member=gemfire-cluster-locator-0}}
{{ Logs exported to the connected member's file system: 
/path/exportedLogs_1612374651595.zip}}{{Barry Oglesby 44 minutes ago}}{{The 
ExportLogsCommand gets all the members including the 
locators:}}{{Set targetMembers = 
getMembersIncludingLocators(groups, memberIds);}}{{I tried a test by changing 
ExportStackTraceCommand.exportStackTrace:}}{{From:}}{{Set 
targetMembers = getMembers(group, 
memberNameOrId);}}{{To:}}{{Set targetMembers = 
getMembersIncludingLocators(group, memberNameOrId);}}{{And the locator stack 
was exported:}}
 * 
 ** 
 *** {{Stack-trace for member locator at 2021/02/03 10:01:28.824 ***}}


> Revise docs to match current gfsh export stack-traces behavior
> --
>
> Key: GEODE-8917
> URL: https://issues.apache.org/jira/browse/GEODE-8917
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> Our docs for gfsh export stack-traces do not match the current behavior. 
> Update the docs.
> {{Shelley Hughes-Godfrey 6:48 PM}}{{I have a question about gfsh export 
> stack-traces ...}}{{"list members" shows me servers and locators 
> ...}}{{gfsh>list members}}
>  \{{ Member Count : 3}}
>  \{{ Name | Id}}
>  \{{ - | 
> }}
>  \{{ gemfire-cluster-server-0 | 
> xx.xx.x.xxx(gemfire-cluster-server-0:1):41000}}
>  {{ gemfire-cluster-locator-0 | 
> 

[jira] [Assigned] (GEODE-8917) Revise docs to match current gfsh export stack-traces behavior

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-8917:
--

Assignee: Karen Smoler Miller

> Revise docs to match current gfsh export stack-traces behavior
> --
>
> Key: GEODE-8917
> URL: https://issues.apache.org/jira/browse/GEODE-8917
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> Our docs for gfsh export stack-traces do not match the current behavior. 
> Update the docs.
> {{Shelley Hughes-Godfrey 6:48 PM}}{{I have a question about gfsh export 
> stack-traces ...}}{{"list members" shows me servers and locators 
> ...}}{{gfsh>list members}}
> {{ Member Count : 3}}
> {{ Name | Id}}
> {{ - | 
> }}
> {{ gemfire-cluster-server-0 | 
> xx.xx.x.xxx(gemfire-cluster-server-0:1):41000}}
> {{ gemfire-cluster-locator-0 | 
> xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]}}
> {{ gemfire-cluster-server-1 | 
> xx.xx.x.xxx(gemfire-cluster-server-1:1):41000}}{{But, if I don't specify 
> members on the export stack-traces command, I just get the stacks for the 
> servers.}}{{gfsh>export stack-traces}}
> {{ stack-trace(s) exported to file: /path/stacktrace_1612316330340}}
> {{ On host : ...}}{{Specifying a locator returns "No Members 
> found"}}{{gfsh>export stack-traces --member=gemfire-cluster-locator-0}}
> {{ No Members Found}}{{Barry Oglesby 2 hours ago}}
> {{ That command excludes the locators. It uses this method in ManagementUtils 
> to get just the normal members:}}{{public static Set 
> getAllNormalMembers(InternalCache cache) {}}
> {{ return new HashSet(}}
> {{ cache.getDistributionManager().getNormalDistributionManagerIds());}}
> {{ }}}{{Shelley Hughes-Godfrey 1 hour ago}}{{So, I also ran "export logs" 
> with --member=}}{{And that works}}{{gfsh>list members}}
> {{ Member Count : 3}}
> {{ Name | Id}}
> {{ - | 
> }}
> {{ gemfire-cluster-server-0 | 
> xx.xx.x.xxx(gemfire-cluster-server-0:1):41000}}
> {{ gemfire-cluster-locator-0 | 
> xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]}}
> {{ gemfire-cluster-server-1 | 
> xx.xx.x.xxx(gemfire-cluster-server-1:1):41000}}{{gfsh>export logs 
> --member=gemfire-cluster-locator-0}}
> {{ Logs exported to the connected member's file system: 
> /path/exportedLogs_1612374651595.zip}}{{Barry Oglesby 44 minutes ago}}{{The 
> ExportLogsCommand gets all the members including the 
> locators:}}{{Set targetMembers = 
> getMembersIncludingLocators(groups, memberIds);}}{{I tried a test by changing 
> ExportStackTraceCommand.exportStackTrace:}}{{From:}}{{Set 
> targetMembers = getMembers(group, 
> memberNameOrId);}}{{To:}}{{Set targetMembers = 
> getMembersIncludingLocators(group, memberNameOrId);}}{{And the locator stack 
> was exported:}}
>  * 
>  ** 
>  *** {{Stack-trace for member locator at 2021/02/03 10:01:28.824 ***}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-8916) The gfsh export stack traces command should include the locators

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller updated GEODE-8916:
---
Description: 
The gfsh export stack traces command should include the locators, but only 
includes the servers.

Here is an excerpt from a slack conversation showing the behavior:
{noformat}
Shelley Hughes-Godfrey  6:48 PM

I have a question about gfsh export stack-traces ...

"list members" shows me servers and locators ...

gfsh>list members
Member Count : 3
  Name| Id
- | 

gemfire-cluster-server-0  | xx.xx.x.xxx(gemfire-cluster-server-0:1):41000
gemfire-cluster-locator-0 | 
xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]
gemfire-cluster-server-1  | xx.xx.x.xxx(gemfire-cluster-server-1:1):41000

But, if I don't specify members on the export stack-traces command, I just get 
the stacks for the servers.

gfsh>export stack-traces
stack-trace(s) exported to file: /path/stacktrace_1612316330340
On host : ...

Specifying a locator returns "No Members found"

gfsh>export stack-traces --member=gemfire-cluster-locator-0
No Members Found




Also, it looks like copy-paste was done from export logs => export stack-traces 
(for --members and --groups).


  was:
The gfsh export stack traces command should include the locators, but only 
includes the servers.

Here is an excerpt from a slack conversation showing the behavior:
{noformat}
Shelley Hughes-Godfrey  6:48 PM

I have a question about gfsh export stack-traces ...

"list members" shows me servers and locators ...

gfsh>list members
Member Count : 3
  Name| Id
- | 

gemfire-cluster-server-0  | xx.xx.x.xxx(gemfire-cluster-server-0:1):41000
gemfire-cluster-locator-0 | 
xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]
gemfire-cluster-server-1  | xx.xx.x.xxx(gemfire-cluster-server-1:1):41000

But, if I don't specify members on the export stack-traces command, I just get 
the stacks for the servers.

gfsh>export stack-traces
stack-trace(s) exported to file: /path/stacktrace_1612316330340
On host : ...

Specifying a locator returns "No Members found"

gfsh>export stack-traces --member=gemfire-cluster-locator-0
No Members Found

Barry Oglesby  2 hours ago
That command excludes the locators. It uses this method in ManagementUtils to 
get just the normal members:

public static Set getAllNormalMembers(InternalCache cache) {
  return new HashSet(
  cache.getDistributionManager().getNormalDistributionManagerIds());
}



{noformat}


> The gfsh export stack traces command should include the locators
> 
>
> Key: GEODE-8916
> URL: https://issues.apache.org/jira/browse/GEODE-8916
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Barrett Oglesby
>Priority: Major
>  Labels: pull-request-available
>
> The gfsh export stack traces command should include the locators, but only 
> includes the servers.
> Here is an excerpt from a slack conversation showing the behavior:
> {noformat}
> Shelley Hughes-Godfrey  6:48 PM
> I have a question about gfsh export stack-traces ...
> "list members" shows me servers and locators ...
> gfsh>list members
> Member Count : 3
>   Name| Id
> - | 
> 
> gemfire-cluster-server-0  | xx.xx.x.xxx(gemfire-cluster-server-0:1):41000
> gemfire-cluster-locator-0 | 
> xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]
> gemfire-cluster-server-1  | xx.xx.x.xxx(gemfire-cluster-server-1:1):41000
> But, if I don't specify members on the export stack-traces command, I just 
> get the stacks for the servers.
> gfsh>export stack-traces
> stack-trace(s) exported to file: /path/stacktrace_1612316330340
> On host : ...
> Specifying a locator returns "No Members found"
> gfsh>export stack-traces --member=gemfire-cluster-locator-0
> No Members Found
> Also, it looks like copy-paste was done from export logs => export 
> stack-traces (for --members and --groups).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-8916) The gfsh export stack traces command should include the locators

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller updated GEODE-8916:
---
Description: 
The gfsh export stack traces command should include the locators, but only 
includes the servers.

Here is an excerpt from a slack conversation showing the behavior:
{noformat}
Shelley Hughes-Godfrey  6:48 PM

I have a question about gfsh export stack-traces ...

"list members" shows me servers and locators ...

gfsh>list members
Member Count : 3
  Name| Id
- | 

gemfire-cluster-server-0  | xx.xx.x.xxx(gemfire-cluster-server-0:1):41000
gemfire-cluster-locator-0 | 
xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]
gemfire-cluster-server-1  | xx.xx.x.xxx(gemfire-cluster-server-1:1):41000

But, if I don't specify members on the export stack-traces command, I just get 
the stacks for the servers.

gfsh>export stack-traces
stack-trace(s) exported to file: /path/stacktrace_1612316330340
On host : ...

Specifying a locator returns "No Members found"

gfsh>export stack-traces --member=gemfire-cluster-locator-0
No Members Found

Barry Oglesby  2 hours ago
That command excludes the locators. It uses this method in ManagementUtils to 
get just the normal members:

public static Set getAllNormalMembers(InternalCache cache) {
  return new HashSet(
  cache.getDistributionManager().getNormalDistributionManagerIds());
}



{noformat}

  was:
The gfsh export stack traces command should include the locators, but only 
includes the servers.

Here is an excerpt from a slack conversation showing the behavior:
{noformat}
Shelley Hughes-Godfrey  6:48 PM

I have a question about gfsh export stack-traces ...

"list members" shows me servers and locators ...

gfsh>list members
Member Count : 3
  Name| Id
- | 

gemfire-cluster-server-0  | xx.xx.x.xxx(gemfire-cluster-server-0:1):41000
gemfire-cluster-locator-0 | 
xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]
gemfire-cluster-server-1  | xx.xx.x.xxx(gemfire-cluster-server-1:1):41000

But, if I don't specify members on the export stack-traces command, I just get 
the stacks for the servers.

gfsh>export stack-traces
stack-trace(s) exported to file: /path/stacktrace_1612316330340
On host : ...

Specifying a locator returns "No Members found"

gfsh>export stack-traces --member=gemfire-cluster-locator-0
No Members Found

Barry Oglesby  2 hours ago
That command excludes the locators. It uses this method in ManagementUtils to 
get just the normal members:

public static Set getAllNormalMembers(InternalCache cache) {
  return new HashSet(
  cache.getDistributionManager().getNormalDistributionManagerIds());
}

Shelley Hughes-Godfrey  1 hour ago

So, I also ran "export logs" with --member=

And that works

gfsh>list members
Member Count : 3
  Name| Id
- | 

gemfire-cluster-server-0  | xx.xx.x.xxx(gemfire-cluster-server-0:1):41000
gemfire-cluster-locator-0 | 
xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]
gemfire-cluster-server-1  | xx.xx.x.xxx(gemfire-cluster-server-1:1):41000

gfsh>export logs --member=gemfire-cluster-locator-0
Logs exported to the connected member's file system: 
/path/exportedLogs_1612374651595.zip

Barry Oglesby  44 minutes ago

The ExportLogsCommand gets all the members including the locators:

Set targetMembers = getMembersIncludingLocators(groups, 
memberIds);

I tried a test by changing ExportStackTraceCommand.exportStackTrace:

From:

Set targetMembers = getMembers(group, memberNameOrId);

To:

Set targetMembers = getMembersIncludingLocators(group, 
memberNameOrId);

And the locator stack was exported:

*** Stack-trace for member locator at 2021/02/03 10:01:28.824 ***
{noformat}


> The gfsh export stack traces command should include the locators
> 
>
> Key: GEODE-8916
> URL: https://issues.apache.org/jira/browse/GEODE-8916
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Barrett Oglesby
>Priority: Major
>  Labels: pull-request-available
>
> The gfsh export stack traces command should include the locators, but only 
> includes the servers.
> Here is an excerpt from a slack conversation showing the behavior:
> {noformat}
> Shelley Hughes-Godfrey  6:48 PM
> I have a question about gfsh export stack-traces ...
> "list members" shows me servers and locators ...
> gfsh>list members
> Member Count : 3
>   Name| Id
> 

[jira] [Created] (GEODE-8917) Revise docs to match current gfsh export stack-traces behavior

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-8917:
--

 Summary: Revise docs to match current gfsh export stack-traces 
behavior
 Key: GEODE-8917
 URL: https://issues.apache.org/jira/browse/GEODE-8917
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


Our docs for gfsh export stack-traces do not match the current behavior. Update 
the docs.

{{Shelley Hughes-Godfrey 6:48 PM}}{{I have a question about gfsh export 
stack-traces ...}}{{"list members" shows me servers and locators 
...}}{{gfsh>list members}}
{{ Member Count : 3}}
{{ Name | Id}}
{{ - | 
}}
{{ gemfire-cluster-server-0 | 
xx.xx.x.xxx(gemfire-cluster-server-0:1):41000}}
{{ gemfire-cluster-locator-0 | 
xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]}}
{{ gemfire-cluster-server-1 | 
xx.xx.x.xxx(gemfire-cluster-server-1:1):41000}}{{But, if I don't specify 
members on the export stack-traces command, I just get the stacks for the 
servers.}}{{gfsh>export stack-traces}}
{{ stack-trace(s) exported to file: /path/stacktrace_1612316330340}}
{{ On host : ...}}{{Specifying a locator returns "No Members 
found"}}{{gfsh>export stack-traces --member=gemfire-cluster-locator-0}}
{{ No Members Found}}{{Barry Oglesby 2 hours ago}}
{{ That command excludes the locators. It uses this method in ManagementUtils 
to get just the normal members:}}{{public static Set 
getAllNormalMembers(InternalCache cache) {}}
{{ return new HashSet(}}
{{ cache.getDistributionManager().getNormalDistributionManagerIds());}}
{{ }}}{{Shelley Hughes-Godfrey 1 hour ago}}{{So, I also ran "export logs" with 
--member=}}{{And that works}}{{gfsh>list members}}
{{ Member Count : 3}}
{{ Name | Id}}
{{ - | 
}}
{{ gemfire-cluster-server-0 | 
xx.xx.x.xxx(gemfire-cluster-server-0:1):41000}}
{{ gemfire-cluster-locator-0 | 
xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]}}
{{ gemfire-cluster-server-1 | 
xx.xx.x.xxx(gemfire-cluster-server-1:1):41000}}{{gfsh>export logs 
--member=gemfire-cluster-locator-0}}
{{ Logs exported to the connected member's file system: 
/path/exportedLogs_1612374651595.zip}}{{Barry Oglesby 44 minutes ago}}{{The 
ExportLogsCommand gets all the members including the 
locators:}}{{Set targetMembers = 
getMembersIncludingLocators(groups, memberIds);}}{{I tried a test by changing 
ExportStackTraceCommand.exportStackTrace:}}{{From:}}{{Set 
targetMembers = getMembers(group, 
memberNameOrId);}}{{To:}}{{Set targetMembers = 
getMembersIncludingLocators(group, memberNameOrId);}}{{And the locator stack 
was exported:}}
 * 
 ** 
 *** {{Stack-trace for member locator at 2021/02/03 10:01:28.824 ***}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-8916) The gfsh export stack traces command should include the locators

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller updated GEODE-8916:
---
Component/s: docs

> The gfsh export stack traces command should include the locators
> 
>
> Key: GEODE-8916
> URL: https://issues.apache.org/jira/browse/GEODE-8916
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Barrett Oglesby
>Priority: Major
>
> The gfsh export stack traces command should include the locators, but only 
> includes the servers.
> Here is an excerpt from a slack conversation showing the behavior:
> {noformat}
> Shelley Hughes-Godfrey  6:48 PM
> I have a question about gfsh export stack-traces ...
> "list members" shows me servers and locators ...
> gfsh>list members
> Member Count : 3
>   Name| Id
> - | 
> 
> gemfire-cluster-server-0  | xx.xx.x.xxx(gemfire-cluster-server-0:1):41000
> gemfire-cluster-locator-0 | 
> xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]
> gemfire-cluster-server-1  | xx.xx.x.xxx(gemfire-cluster-server-1:1):41000
> But, if I don't specify members on the export stack-traces command, I just 
> get the stacks for the servers.
> gfsh>export stack-traces
> stack-trace(s) exported to file: /path/stacktrace_1612316330340
> On host : ...
> Specifying a locator returns "No Members found"
> gfsh>export stack-traces --member=gemfire-cluster-locator-0
> No Members Found
> Barry Oglesby  2 hours ago
> That command excludes the locators. It uses this method in ManagementUtils to 
> get just the normal members:
> public static Set getAllNormalMembers(InternalCache cache) 
> {
>   return new HashSet(
>   cache.getDistributionManager().getNormalDistributionManagerIds());
> }
> Shelley Hughes-Godfrey  1 hour ago
> So, I also ran "export logs" with --member=
> And that works
> gfsh>list members
> Member Count : 3
>   Name| Id
> - | 
> 
> gemfire-cluster-server-0  | xx.xx.x.xxx(gemfire-cluster-server-0:1):41000
> gemfire-cluster-locator-0 | 
> xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator):41000 [Coordinator]
> gemfire-cluster-server-1  | xx.xx.x.xxx(gemfire-cluster-server-1:1):41000
> gfsh>export logs --member=gemfire-cluster-locator-0
> Logs exported to the connected member's file system: 
> /path/exportedLogs_1612374651595.zip
> Barry Oglesby  44 minutes ago
> The ExportLogsCommand gets all the members including the locators:
> Set targetMembers = getMembersIncludingLocators(groups, 
> memberIds);
> I tried a test by changing ExportStackTraceCommand.exportStackTrace:
> From:
> Set targetMembers = getMembers(group, memberNameOrId);
> To:
> Set targetMembers = getMembersIncludingLocators(group, 
> memberNameOrId);
> And the locator stack was exported:
> *** Stack-trace for member locator at 2021/02/03 10:01:28.824 ***
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-8850) Revise security-client-auth-init property defn

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-8850.

Fix Version/s: 1.14.0
   Resolution: Fixed

> Revise security-client-auth-init property defn
> --
>
> Key: GEODE-8850
> URL: https://issues.apache.org/jira/browse/GEODE-8850
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.14.0
>
>
> It appears that the definition of the security-client-auth-init property is 
> simply a copy of the security-peer-auth-init property definition. Revise it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (GEODE-8850) Revise security-client-auth-init property defn

[Karen Smoler Miller (Jira)]

[ 
https://issues.apache.org/jira/browse/GEODE-8850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17269563#comment-17269563
 ] 

Karen Smoler Miller commented on GEODE-8850:


This JIRA needs to be expanded.  Not only is the security-client-auth-init 
property definition wrong, but the security-peer-auth-init property definition 
is also wrong. And, the information given at 
https://geode.apache.org/docs/guide/113/managing/security/implementing_authentication.html
 is wrong (for how both servers and clients set their credentials).

> Revise security-client-auth-init property defn
> --
>
> Key: GEODE-8850
> URL: https://issues.apache.org/jira/browse/GEODE-8850
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
>
> It appears that the definition of the security-client-auth-init property is 
> simply a copy of the security-peer-auth-init property definition. Revise it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-8850) Revise security-client-auth-init property defn

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-8850:
--

 Summary: Revise security-client-auth-init property defn
 Key: GEODE-8850
 URL: https://issues.apache.org/jira/browse/GEODE-8850
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


It appears that the definition of the security-client-auth-init property is 
simply a copy of the security-peer-auth-init property definition. Revise it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-8850) Revise security-client-auth-init property defn

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-8850:
--

Assignee: Karen Smoler Miller

> Revise security-client-auth-init property defn
> --
>
> Key: GEODE-8850
> URL: https://issues.apache.org/jira/browse/GEODE-8850
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> It appears that the definition of the security-client-auth-init property is 
> simply a copy of the security-peer-auth-init property definition. Revise it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-8839) Remove unneeded links from docs pages

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-8839.

Fix Version/s: 1.14.0
 Assignee: Karen Smoler Miller
   Resolution: Fixed

> Remove unneeded links from docs pages
> -
>
> Key: GEODE-8839
> URL: https://issues.apache.org/jira/browse/GEODE-8839
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.14.0
>
>
> The prose/content for sections within Developing , Events and Event Handling 
> , Configuring Client/Server Event Messaging includes a list of links to other 
> sections that already appear in the subnav. Some of those linked sections 
> also include a list links.  The links are irrelevant and don't help readers 
> of the documentation, so remove the links.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-8829) Improve copy-on-read docs

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-8829.

Fix Version/s: 1.14.0
   Resolution: Fixed

> Improve copy-on-read docs
> -
>
> Key: GEODE-8829
> URL: https://issues.apache.org/jira/browse/GEODE-8829
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.14.0
>
>
> The section describing copy-on-read is incomplete. Add two other ways to set 
> copy-on-read to true:
> 1. Use the API GemFireCache.setCopyOnRead() method; Cache inherits this 
> method, so an example would show Cache.setCopyOnRead() in use.
> 2. The gfsh alter runtime has an option to set copy-on-read to true. Use this 
> once servers are running.
> At the same time, update the example that demonstrates making a copy. Add 
> prose to the current example to explain why the put call belongs in this 
> example.  Or, revise the example to show only the making of the copy.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-8839) Remove unneeded links from docs pages

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-8839:
--

 Summary: Remove unneeded links from docs pages
 Key: GEODE-8839
 URL: https://issues.apache.org/jira/browse/GEODE-8839
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


The prose/content for sections within Developing , Events and Event Handling , 
Configuring Client/Server Event Messaging includes a list of links to other 
sections that already appear in the subnav. Some of those linked sections also 
include a list links.  The links are irrelevant and don't help readers of the 
documentation, so remove the links.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-8829) Improve copy-on-read docs

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-8829:
--

Assignee: Karen Smoler Miller

> Improve copy-on-read docs
> -
>
> Key: GEODE-8829
> URL: https://issues.apache.org/jira/browse/GEODE-8829
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> The section describing copy-on-read is incomplete. Add two other ways to set 
> copy-on-read to true:
> 1. Use the API GemFireCache.setCopyOnRead() method; Cache inherits this 
> method, so an example would show Cache.setCopyOnRead() in use.
> 2. The gfsh alter runtime has an option to set copy-on-read to true. Use this 
> once servers are running.
> At the same time, update the example that demonstrates making a copy. Add 
> prose to the current example to explain why the put call belongs in this 
> example.  Or, revise the example to show only the making of the copy.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-8826) Warn readers that post processor callback receives a reference

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-8826.

Fix Version/s: 1.14.0
   Resolution: Fixed

> Warn readers that post processor callback receives a reference
> --
>
> Key: GEODE-8826
> URL: https://issues.apache.org/jira/browse/GEODE-8826
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.14.0
>
>
> When the copy-on-read attribute is not set to true, the 
> org.apache.geode.security.PostProcessor.processRegionValue is given 
> references to the region entry's key and value. We need to explicitly warn 
> readers of the docs section on post processing data of this, so they don't 
> accidentally modify the region entries.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-8829) Improve copy-on-read docs

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-8829:
--

 Summary: Improve copy-on-read docs
 Key: GEODE-8829
 URL: https://issues.apache.org/jira/browse/GEODE-8829
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


The section describing copy-on-read is incomplete. Add two other ways to set 
copy-on-read to true:
1. Use the API GemFireCache.setCopyOnRead() method; Cache inherits this method, 
so an example would show Cache.setCopyOnRead() in use.
2. The gfsh alter runtime has an option to set copy-on-read to true. Use this 
once servers are running.

At the same time, update the example that demonstrates making a copy. Add prose 
to the current example to explain why the put call belongs in this example.  
Or, revise the example to show only the making of the copy.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-8828) Docs improvement: state that region names are case sensitive

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-8828.

Fix Version/s: 1.14.0
   Resolution: Fixed

> Docs improvement: state that region names are case sensitive
> 
>
> Key: GEODE-8828
> URL: https://issues.apache.org/jira/browse/GEODE-8828
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.14.0
>
>
> Our docs should explicitly state that region names are case sensitive. The 
> right place to put this info is the section called Region Naming.  That 
> section is within the Basic Configuration and Programming, Data Regions 
> section.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-7101) User Guide - explicitly state that region names are case-sensitive

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-7101.

Resolution: Duplicate

Duplicate of GEODE-8828. Resolving this issue.

> User Guide - explicitly state that region names are case-sensitive
> --
>
> Key: GEODE-7101
> URL: https://issues.apache.org/jira/browse/GEODE-7101
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Minor
>
> Add a note to the "Region Naming" page stating explicitly that region names 
> are case-sensitive: 
> [https://geode.apache.org/docs/guide/19/basic_config/data_regions/region_naming.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (GEODE-7101) User Guide - explicitly state that region names are case-sensitive

[Karen Smoler Miller (Jira)]

[ 
https://issues.apache.org/jira/browse/GEODE-7101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17263701#comment-17263701
 ] 

Karen Smoler Miller commented on GEODE-7101:


Fix filed under a PR for GEODE-8828. 

> User Guide - explicitly state that region names are case-sensitive
> --
>
> Key: GEODE-7101
> URL: https://issues.apache.org/jira/browse/GEODE-7101
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Minor
>
> Add a note to the "Region Naming" page stating explicitly that region names 
> are case-sensitive: 
> [https://geode.apache.org/docs/guide/19/basic_config/data_regions/region_naming.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-8828) Docs improvement: state that region names are case sensitive

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-8828:
--

Assignee: Karen Smoler Miller

> Docs improvement: state that region names are case sensitive
> 
>
> Key: GEODE-8828
> URL: https://issues.apache.org/jira/browse/GEODE-8828
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> Our docs should explicitly state that region names are case sensitive. The 
> right place to put this info is the section called Region Naming.  That 
> section is within the Basic Configuration and Programming, Data Regions 
> section.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-8828) Docs improvement: state that region names are case sensitive

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-8828:
--

 Summary: Docs improvement: state that region names are case 
sensitive
 Key: GEODE-8828
 URL: https://issues.apache.org/jira/browse/GEODE-8828
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


Our docs should explicitly state that region names are case sensitive. The 
right place to put this info is the section called Region Naming.  That section 
is within the Basic Configuration and Programming, Data Regions section.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-8826) Warn readers that post processor callback receives a reference

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-8826:
--

Assignee: Karen Smoler Miller

> Warn readers that post processor callback receives a reference
> --
>
> Key: GEODE-8826
> URL: https://issues.apache.org/jira/browse/GEODE-8826
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> When the copy-on-read attribute is not set to true, the 
> org.apache.geode.security.PostProcessor.processRegionValue is given 
> references to the region entry's key and value. We need to explicitly warn 
> readers of the docs section on post processing data of this, so they don't 
> accidentally modify the region entries.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-8818) Make docs of copy-on-read more visible to readers

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-8818:
--

Assignee: Karen Smoler Miller

> Make docs of copy-on-read more visible to readers
> -
>
> Key: GEODE-8818
> URL: https://issues.apache.org/jira/browse/GEODE-8818
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> Our users need more visibility of the copy-on-read region attribute. Promote 
> the subsection from within Basic Configuration and Programming, Data Entries, 
> Managing Data Entries to its own section within Data Entries. Update all 
> links within the manual to point to the new section.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-8818) Make docs of copy-on-read more visible to readers

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller updated GEODE-8818:
---
Description: Our users need more visibility of the copy-on-read region 
attribute. Promote the subsection from within Basic Configuration and 
Programming, Data Entries, Managing Data Entries to its own section within Data 
Entries. Update all links within the manual to point to the new section.  (was: 
Our users need more visibility of the copy-on-read region attribute. Promote it 
from within Basic Configuration and Programming, Data Entries, Managing Data 
Entries to its own section within Data Entries. Update all links within the 
manual to point to the new section.)

> Make docs of copy-on-read more visible to readers
> -
>
> Key: GEODE-8818
> URL: https://issues.apache.org/jira/browse/GEODE-8818
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Priority: Major
>
> Our users need more visibility of the copy-on-read region attribute. Promote 
> the subsection from within Basic Configuration and Programming, Data Entries, 
> Managing Data Entries to its own section within Data Entries. Update all 
> links within the manual to point to the new section.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-8818) Make docs of copy-on-read more visible to readers

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller updated GEODE-8818:
---
Description: Our users need more visibility of the copy-on-read region 
attribute. Promote it from within Basic Configuration and Programming - Data 
Entries - Managing Data Entries to its own section within Data Entries. Update 
all links within the manual to point to the new section.  (was: Our users need 
more visibility of the copy-on-read region attribute. Promote it from within 
_Basic Configuration and Programming_ - _Data Entries_ - _Managing Data 
Entries_ to its own section within _Data Entries_. Update all links within the 
manual to point to the new section.)

> Make docs of copy-on-read more visible to readers
> -
>
> Key: GEODE-8818
> URL: https://issues.apache.org/jira/browse/GEODE-8818
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Priority: Major
>
> Our users need more visibility of the copy-on-read region attribute. Promote 
> it from within Basic Configuration and Programming - Data Entries - Managing 
> Data Entries to its own section within Data Entries. Update all links within 
> the manual to point to the new section.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-8818) Make docs of copy-on-read more visible to readers

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller updated GEODE-8818:
---
Description: Our users need more visibility of the copy-on-read region 
attribute. Promote it from within Basic Configuration and Programming, Data 
Entries, Managing Data Entries to its own section within Data Entries. Update 
all links within the manual to point to the new section.  (was: Our users need 
more visibility of the copy-on-read region attribute. Promote it from within 
Basic Configuration and Programming - Data Entries - Managing Data Entries to 
its own section within Data Entries. Update all links within the manual to 
point to the new section.)

> Make docs of copy-on-read more visible to readers
> -
>
> Key: GEODE-8818
> URL: https://issues.apache.org/jira/browse/GEODE-8818
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Priority: Major
>
> Our users need more visibility of the copy-on-read region attribute. Promote 
> it from within Basic Configuration and Programming, Data Entries, Managing 
> Data Entries to its own section within Data Entries. Update all links within 
> the manual to point to the new section.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-8818) Make docs of copy-on-read more visible to readers

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller updated GEODE-8818:
---
Description: Our users need more visibility of the copy-on-read region 
attribute. Promote it from within _Basic Configuration and Programming_ - _Data 
Entries_ - _Managing Data Entries_ to its own section within _Data Entries_. 
Update all links within the manual to point to the new section.  (was: Our 
users need more visibility of the copy-on-read region attribute. Promote it 
from within _Basic Configuration and Programming_ -> _Data Entries_ -> 
_Managing Data Entries_ to its own section within _Data Entries_. Update all 
links within the manual to point to the new section.)

> Make docs of copy-on-read more visible to readers
> -
>
> Key: GEODE-8818
> URL: https://issues.apache.org/jira/browse/GEODE-8818
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Priority: Major
>
> Our users need more visibility of the copy-on-read region attribute. Promote 
> it from within _Basic Configuration and Programming_ - _Data Entries_ - 
> _Managing Data Entries_ to its own section within _Data Entries_. Update all 
> links within the manual to point to the new section.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-8818) Make docs of copy-on-read more visible to readers

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-8818:
--

 Summary: Make docs of copy-on-read more visible to readers
 Key: GEODE-8818
 URL: https://issues.apache.org/jira/browse/GEODE-8818
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


Our users need more visibility of the copy-on-read region attribute. Promote it 
from within _Basic Configuration and Programming_ -> _Data Entries_ -> 
_Managing Data Entries_ to its own section within _Data Entries_. Update all 
links within the manual to point to the new section.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-8802) Clarify mcast-port default in Docs

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-8802.

Fix Version/s: 1.14.0
   Resolution: Fixed

> Clarify mcast-port default in Docs
> --
>
> Key: GEODE-8802
> URL: https://issues.apache.org/jira/browse/GEODE-8802
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.14.0
>
>
> In 
> [https://geode.apache.org/docs/guide/113/configuring/running/firewalls_ports.html,]
>  in the subsection called Default Port Configurations, the default port value 
> for mcast-port is not quite correct.  It says the default is 10334.  It 
> should instead say that the default is 0 when the locators property is set, 
> and 10334 when the locators property is not set.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-8804) Tell readers about data loss possibility in partitioned regions

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-8804.

Fix Version/s: 1.14.0
   Resolution: Fixed

> Tell readers about data loss possibility in partitioned regions
> ---
>
> Key: GEODE-8804
> URL: https://issues.apache.org/jira/browse/GEODE-8804
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.14.0
>
>
> In the Partitioned Regions section of 
> [https://geode.apache.org/docs/guide/113/developing/region_options/region_types.html,]
>  we highlight the high availability nature of partitioned regions, but 
> neglect to mention the association between the quantity of redundant copies 
> and the quantity of server failures that could lead to data loss.
> This doc improvement will clarify the issue, so that developers will not 
> falsely believe that just using a partitioned region eliminates the 
> possibility of data loss.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-8804) Tell readers about data loss possibility in partitioned regions

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-8804:
--

Assignee: Karen Smoler Miller

> Tell readers about data loss possibility in partitioned regions
> ---
>
> Key: GEODE-8804
> URL: https://issues.apache.org/jira/browse/GEODE-8804
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> In the Partitioned Regions section of 
> [https://geode.apache.org/docs/guide/113/developing/region_options/region_types.html,]
>  we highlight the high availability nature of partitioned regions, but 
> neglect to mention the association between the quantity of redundant copies 
> and the quantity of server failures that could lead to data loss.
> This doc improvement will clarify the issue, so that developers will not 
> falsely believe that just using a partitioned region eliminates the 
> possibility of data loss.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-8804) Tell readers about data loss possibility in partitioned regions

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-8804:
--

 Summary: Tell readers about data loss possibility in partitioned 
regions
 Key: GEODE-8804
 URL: https://issues.apache.org/jira/browse/GEODE-8804
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


In the Partitioned Regions section of 
[https://geode.apache.org/docs/guide/113/developing/region_options/region_types.html,]
 we highlight the high availability nature of partitioned regions, but neglect 
to mention the association between the quantity of redundant copies and the 
quantity of server failures that could lead to data loss.

This doc improvement will clarify the issue, so that developers will not 
falsely believe that just using a partitioned region eliminates the possibility 
of data loss.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (GEODE-8802) Clarify mcast-port default in Docs

[Karen Smoler Miller (Jira)]

[ 
https://issues.apache.org/jira/browse/GEODE-8802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17258593#comment-17258593
 ] 

Karen Smoler Miller commented on GEODE-8802:


[~bschuchardt] says that the description is wrong in this ticket. mcast-port 
always defaults to zero.

> Clarify mcast-port default in Docs
> --
>
> Key: GEODE-8802
> URL: https://issues.apache.org/jira/browse/GEODE-8802
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
>
> In 
> [https://geode.apache.org/docs/guide/113/configuring/running/firewalls_ports.html,]
>  in the subsection called Default Port Configurations, the default port value 
> for mcast-port is not quite correct.  It says the default is 10334.  It 
> should instead say that the default is 0 when the locators property is set, 
> and 10334 when the locators property is not set.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-8802) Clarify mcast-port default in Docs

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-8802:
--

Assignee: Karen Smoler Miller

> Clarify mcast-port default in Docs
> --
>
> Key: GEODE-8802
> URL: https://issues.apache.org/jira/browse/GEODE-8802
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> In 
> [https://geode.apache.org/docs/guide/113/configuring/running/firewalls_ports.html,]
>  in the subsection called Default Port Configurations, the default port value 
> for mcast-port is not quite correct.  It says the default is 10334.  It 
> should instead say that the default is 0 when the locators property is set, 
> and 10334 when the locators property is not set.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-8802) Clarify mcast-port default in Docs

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-8802:
--

 Summary: Clarify mcast-port default in Docs
 Key: GEODE-8802
 URL: https://issues.apache.org/jira/browse/GEODE-8802
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


In 
[https://geode.apache.org/docs/guide/113/configuring/running/firewalls_ports.html,]
 in the subsection called Default Port Configurations, the default port value 
for mcast-port is not quite correct.  It says the default is 10334.  It should 
instead say that the default is 0 when the locators property is set, and 10334 
when the locators property is not set.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-8556) Geode docs refer to message that no longer exists

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-8556.

Fix Version/s: 1.14.0
   Resolution: Fixed

> Geode docs refer to message that no longer exists
> -
>
> Key: GEODE-8556
> URL: https://issues.apache.org/jira/browse/GEODE-8556
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Dan Smith
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.14.0
>
>
> This [Starting up and Shutting 
> Down|https://geode.apache.org/docs/guide/12/configuring/running/starting_up_shutting_down.html]
>  refers to an info level message "GemFire startup was unable to contact a 
> locator. Waiting for one to start. ..."
> This message is from an older version of GemFire, it is no longer present in 
> current versions of the system.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-8556) Geode docs refer to message that no longer exists

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-8556:
--

Assignee: Karen Smoler Miller

> Geode docs refer to message that no longer exists
> -
>
> Key: GEODE-8556
> URL: https://issues.apache.org/jira/browse/GEODE-8556
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Dan Smith
>Assignee: Karen Smoler Miller
>Priority: Major
>
> This [Starting up and Shutting 
> Down|https://geode.apache.org/docs/guide/12/configuring/running/starting_up_shutting_down.html]
>  refers to an info level message "GemFire startup was unable to contact a 
> locator. Waiting for one to start. ..."
> This message is from an older version of GemFire, it is no longer present in 
> current versions of the system.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-8410) Remove offensive wording from documentation

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-8410.

Fix Version/s: 1.14.0
   Resolution: Fixed

> Remove offensive wording from documentation
> ---
>
> Key: GEODE-8410
> URL: https://issues.apache.org/jira/browse/GEODE-8410
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.14.0
>
>
> Offensive wording appears in our documentation.  We should rewrite to 
> eliminate the offensive wording.
> Here are some examples and possible substitutions:
> abort becomes stop/cancel/stop prematurely
> whitelist and blacklist become allowlist(noun), allow(v) and denylist(noun), 
> deny(v) or block
> blackout becomes restriction(noun), restrict(v)
> master and slave become primary or main and secondary or worker
> whitehat and blackhat become ethical and unethical
> kill becomes stop or halt
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-8410) Remove offensive wording from documentation

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-8410:
--

Assignee: Karen Smoler Miller

> Remove offensive wording from documentation
> ---
>
> Key: GEODE-8410
> URL: https://issues.apache.org/jira/browse/GEODE-8410
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> Offensive wording appears in our documentation.  We should rewrite to 
> eliminate the offensive wording.
> Here are some examples and possible substitutions:
> abort becomes stop/cancel/stop prematurely
> whitelist and blacklist become allowlist(noun), allow(v) and denylist(noun), 
> deny(v) or block
> blackout becomes restriction(noun), restrict(v)
> master and slave become primary or main and secondary or worker
> whitehat and blackhat become ethical and unethical
> kill becomes stop or halt
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-8410) Remove offensive wording from documentation

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller updated GEODE-8410:
---
Description: 
Offensive wording appears in our documentation.  We should rewrite to eliminate 
the offensive wording.

Here are some examples and possible substitutions:

abort becomes stop/cancel/stop prematurely

whitelist and blacklist become allowlist(noun), allow(v) and denylist(noun), 
deny(v) or block

blackout becomes restriction(noun), restrict(v)

master and slave become primary or main and secondary or worker

whitehat and blackhat become ethical and unethical

kill becomes stop or halt

 

  was:
Offensive wording appears in our documentation.  We should rewrite to eliminate 
the offensive wording.

Here are some examples and possible substitutions:

abort becomes stop/cancel/stop prematurely

whitelist and blacklist become allowlist(n), allow(v) and denylist(n), deny(v) 
or block

blackout becomes restriction(n), restrict(v)

master and slave become primary or main and secondary or worker

whitehat and blackhat become ethical and unethical

kill becomes stop or halt

 


> Remove offensive wording from documentation
> ---
>
> Key: GEODE-8410
> URL: https://issues.apache.org/jira/browse/GEODE-8410
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Priority: Major
>
> Offensive wording appears in our documentation.  We should rewrite to 
> eliminate the offensive wording.
> Here are some examples and possible substitutions:
> abort becomes stop/cancel/stop prematurely
> whitelist and blacklist become allowlist(noun), allow(v) and denylist(noun), 
> deny(v) or block
> blackout becomes restriction(noun), restrict(v)
> master and slave become primary or main and secondary or worker
> whitehat and blackhat become ethical and unethical
> kill becomes stop or halt
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-8410) Remove offensive wording from documentation

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-8410:
--

 Summary: Remove offensive wording from documentation
 Key: GEODE-8410
 URL: https://issues.apache.org/jira/browse/GEODE-8410
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


Offensive wording appears in our documentation.  We should rewrite to eliminate 
the offensive wording.

Here are some examples and possible substitutions:

abort becomes stop/cancel/stop prematurely

whitelist and blacklist become allowlist(n), allow(v) and denylist(n), deny(v) 
or block

blackout becomes restriction(n), restrict(v)

master and slave become primary or main and secondary or worker

whitehat and blackhat become ethical and unethical

kill becomes stop or halt

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-8331) allow GFSH to connect to newer and older locator/server.

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller updated GEODE-8331:
---
Component/s: docs

> allow GFSH to connect to newer and older locator/server.
> 
>
> Key: GEODE-8331
> URL: https://issues.apache.org/jira/browse/GEODE-8331
> Project: Geode
>  Issue Type: Bug
>  Components: docs, gfsh
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: GeodeOperationAPI, pull-request-available
>
> When using an older or newer gfsh to connect to an older or newer distributed 
> system gfsh will throw a warning error and not connect.
> Example warning message Cannot use a 9.8.5 gfsh client to connect to a 9.9.0 
> cluster..
> The desired behavior is to allow gfsh connect and only if there is an issue 
> with an updated /unknown command parsing should the system throw an error and 
> provide the extra guidance of what version the servers are at and the version 
> of the current gfsh cli.
> Initially add these capability into the newer product version
> Later based on the feasibility of adding this to older version, this will be 
> ported into the older version.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-8363) Make docs clear that Micrometer API is experimental

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-8363.

Fix Version/s: 1.14.0
   Resolution: Fixed

> Make docs clear that Micrometer API is experimental
> ---
>
> Key: GEODE-8363
> URL: https://issues.apache.org/jira/browse/GEODE-8363
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.14.0
>
>
> The MetricsSession and MetricsPublishingService interfaces are marked as 
> experimental. The docs do not make this clear.  There is a note at the end of 
> a subsection to that effect, but it is definitely not prominent.
> Make the docs clear that the Micrometer API is experimental by putting a note 
> in a more prominent place, such as at the beginning of the section.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-8363) Make docs clear that Micrometer API is experimental

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-8363:
--

Assignee: Karen Smoler Miller

> Make docs clear that Micrometer API is experimental
> ---
>
> Key: GEODE-8363
> URL: https://issues.apache.org/jira/browse/GEODE-8363
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> The MetricsSession and MetricsPublishingService interfaces are marked as 
> experimental. The docs do not make this clear.  There is a note at the end of 
> a subsection to that effect, but it is definitely not prominent.
> Make the docs clear that the Micrometer API is experimental by putting a note 
> in a more prominent place, such as at the beginning of the section.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-8363) Make docs clear that Micrometer API is experimental

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-8363:
--

 Summary: Make docs clear that Micrometer API is experimental
 Key: GEODE-8363
 URL: https://issues.apache.org/jira/browse/GEODE-8363
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


The MetricsSession and MetricsPublishingService interfaces are marked as 
experimental. The docs do not make this clear.  There is a note at the end of a 
subsection to that effect, but it is definitely not prominent.

Make the docs clear that the Micrometer API is experimental by putting a note 
in a more prominent place, such as at the beginning of the section.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-8341) Correct typo in gfsh export docs

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-8341.

Fix Version/s: 1.14.0
   Resolution: Fixed

> Correct typo in gfsh export docs
> 
>
> Key: GEODE-8341
> URL: https://issues.apache.org/jira/browse/GEODE-8341
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
> Fix For: 1.14.0
>
>
> There's a single character typo in the docs.  In the command reference page 
> for 
> gfsh export logs
> the name of the ZIP file is of the form exportedLogs_xxx.zip.  The docs use a 
> lowercase 'l', and it needs to be changed to an uppercase 'L'.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-8341) Correct typo in gfsh export docs

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-8341:
--

Assignee: Karen Smoler Miller

> Correct typo in gfsh export docs
> 
>
> Key: GEODE-8341
> URL: https://issues.apache.org/jira/browse/GEODE-8341
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> There's a single character typo in the docs.  In the command reference page 
> for 
> gfsh export logs
> the name of the ZIP file is of the form exportedLogs_xxx.zip.  The docs use a 
> lowercase 'l', and it needs to be changed to an uppercase 'L'.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-8341) Correct typo in gfsh export docs

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-8341:
--

 Summary: Correct typo in gfsh export docs
 Key: GEODE-8341
 URL: https://issues.apache.org/jira/browse/GEODE-8341
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


There's a single character typo in the docs.  In the command reference page for 
gfsh export logs
the name of the ZIP file is of the form exportedLogs_xxx.zip.  The docs use a 
lowercase 'l', and it needs to be changed to an uppercase 'L'.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-8198) Revise docs to better specify putAll() behavior

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-8198.

Fix Version/s: 1.14.0
   Resolution: Fixed

> Revise docs to better specify putAll() behavior
> ---
>
> Key: GEODE-8198
> URL: https://issues.apache.org/jira/browse/GEODE-8198
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
> Fix For: 1.14.0
>
>
> [GEODE-8171|https://issues.apache.org/jira/browse/GEODE-8171] updated the 
> Javadocs for the Region.putAll() method. Our user guide should also specify 
> the behavior under exceptions and give readers more context such that they 
> can produce better apps.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-8198) Revise docs to better specify putAll() behavior

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-8198:
--

Assignee: Karen Smoler Miller

> Revise docs to better specify putAll() behavior
> ---
>
> Key: GEODE-8198
> URL: https://issues.apache.org/jira/browse/GEODE-8198
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> [GEODE-8171|https://issues.apache.org/jira/browse/GEODE-8171] updated the 
> Javadocs for the Region.putAll() method. Our user guide should also specify 
> the behavior under exceptions and give readers more context such that they 
> can produce better apps.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-8198) Revise docs to better specify putAll() behavior

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-8198:
--

 Summary: Revise docs to better specify putAll() behavior
 Key: GEODE-8198
 URL: https://issues.apache.org/jira/browse/GEODE-8198
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


[GEODE-8171|https://issues.apache.org/jira/browse/GEODE-8171] updated the 
Javadocs for the Region.putAll() method. Our user guide should also specify the 
behavior under exceptions and give readers more context such that they can 
produce better apps.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-8171) javadoc for putAll need to have accurate exception

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller updated GEODE-8171:
---
Description: 
Both the javadocs and the user guide need a more accurate description of the 
exceptions that can be thrown when an app calls putAll().  

Correct the javadocs to list all exceptions that may be thrown.

Add a code fragment example to the user guide (and to the javadocs, if 
appropriate) that shows a best practice for an app to call putAll() and handle 
exceptions.

Describe what might cause the exceptions and let users know how to adjust 
cluster configuration mitigate the exceptions.

> javadoc for putAll need to have accurate exception 
> ---
>
> Key: GEODE-8171
> URL: https://issues.apache.org/jira/browse/GEODE-8171
> Project: Geode
>  Issue Type: Improvement
>Reporter: Xiaojian Zhou
>Assignee: Xiaojian Zhou
>Priority: Major
>
> Both the javadocs and the user guide need a more accurate description of the 
> exceptions that can be thrown when an app calls putAll().  
> Correct the javadocs to list all exceptions that may be thrown.
> Add a code fragment example to the user guide (and to the javadocs, if 
> appropriate) that shows a best practice for an app to call putAll() and 
> handle exceptions.
> Describe what might cause the exceptions and let users know how to adjust 
> cluster configuration mitigate the exceptions.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-8038) Fix product name in docs

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-8038.

Fix Version/s: 1.13.0
   Resolution: Fixed

> Fix product name in docs
> 
>
> Key: GEODE-8038
> URL: https://issues.apache.org/jira/browse/GEODE-8038
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
> Fix For: 1.13.0
>
>
> There are two pages in the docs where we missed updating the docs to use a 
> template variable instead of the product name when donation occurred.  
> Correct this oversight.
>  * File tools_modules/redis_adapter.html.md.erb, the title of the section
>  * File prereq_and_install.html.md.erb in the prose.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-8038) Fix product name in docs

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-8038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-8038:
--

Assignee: Karen Smoler Miller

> Fix product name in docs
> 
>
> Key: GEODE-8038
> URL: https://issues.apache.org/jira/browse/GEODE-8038
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> There are two pages in the docs where we missed updating the docs to use a 
> template variable instead of the product name when donation occurred.  
> Correct this oversight.
>  * File tools_modules/redis_adapter.html.md.erb, the title of the section
>  * File prereq_and_install.html.md.erb in the prose.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-8038) Fix product name in docs

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-8038:
--

 Summary: Fix product name in docs
 Key: GEODE-8038
 URL: https://issues.apache.org/jira/browse/GEODE-8038
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


There are two pages in the docs where we missed updating the docs to use a 
template variable instead of the product name when donation occurred.  Correct 
this oversight.
 * File tools_modules/redis_adapter.html.md.erb, the title of the section
 * File prereq_and_install.html.md.erb in the prose.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-7997) Parallel GS need disk store where their regions are

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-7997.

Fix Version/s: 1.13.0
   Resolution: Fixed

> Parallel GS need disk store where their regions are
> ---
>
> Key: GEODE-7997
> URL: https://issues.apache.org/jira/browse/GEODE-7997
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
> Fix For: 1.13.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Shutdown and startup will hang if their regions and parallel gateway disk 
> stores are separated from each other. They need to be grouped together same 
> as colocated regions. Disk store can differ for serial gateway senders, but 
> parallel ones must be colocated with the regions they are attached to, and 
> colocated regions must be stored in the same disk store to not cause 
> synchronization issues.
> The resolution is to either have one disk store for all gateway senders and 
> regions or group regions and gateway senders logically together in disk 
> stores so each region and its gateway senders are in a particular disk store.
> Document this behavior and the solution.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-7997) Parallel GS need disk store where their regions are

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-7997:
--

Assignee: Karen Smoler Miller

> Parallel GS need disk store where their regions are
> ---
>
> Key: GEODE-7997
> URL: https://issues.apache.org/jira/browse/GEODE-7997
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Shutdown and startup will hang if their regions and parallel gateway disk 
> stores are separated from each other. They need to be grouped together same 
> as colocated regions. Disk store can differ for serial gateway senders, but 
> parallel ones must be colocated with the regions they are attached to, and 
> colocated regions must be stored in the same disk store to not cause 
> synchronization issues.
> The resolution is to either have one disk store for all gateway senders and 
> regions or group regions and gateway senders logically together in disk 
> stores so each region and its gateway senders are in a particular disk store.
> Document this behavior and the solution.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-7997) Parallel GS need disk store where their regions are

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-7997:
--

 Summary: Parallel GS need disk store where their regions are
 Key: GEODE-7997
 URL: https://issues.apache.org/jira/browse/GEODE-7997
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


Shutdown and startup will hang if their regions and parallel gateway disk 
stores are separated from each other. They need to be grouped together same as 
colocated regions. Disk store can differ for serial gateway senders, but 
parallel ones must be colocated with the regions they are attached to, and 
colocated regions must be stored in the same disk store to not cause 
synchronization issues.

The resolution is to either have one disk store for all gateway senders and 
regions or group regions and gateway senders logically together in disk stores 
so each region and its gateway senders are in a particular disk store.

Document this behavior and the solution.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-7993) Gateway senders try to connect once at start up

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-7993.

Fix Version/s: 1.13.0
   Resolution: Fixed

> Gateway senders try to connect once at start up
> ---
>
> Key: GEODE-7993
> URL: https://issues.apache.org/jira/browse/GEODE-7993
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
> Fix For: 1.13.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Document that GW senders try once to connect to GW receivers upon GW sender 
> start up. If there's no receiver present at that time, it is not an error.  
> The GW sender tries again when it has a batch of events to send.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-7993) Gateway senders try to connect once at start up

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-7993:
--

Assignee: Karen Smoler Miller

> Gateway senders try to connect once at start up
> ---
>
> Key: GEODE-7993
> URL: https://issues.apache.org/jira/browse/GEODE-7993
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> Document that GW senders try once to connect to GW receivers upon GW sender 
> start up. If there's no receiver present at that time, it is not an error.  
> The GW sender tries again when it has a batch of events to send.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-7993) Gateway senders try to connect once at start up

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-7993:
--

 Summary: Gateway senders try to connect once at start up
 Key: GEODE-7993
 URL: https://issues.apache.org/jira/browse/GEODE-7993
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


Document that GW senders try once to connect to GW receivers upon GW sender 
start up. If there's no receiver present at that time, it is not an error.  The 
GW sender tries again when it has a batch of events to send.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-7835) Correct doc typo of file name gfsecurity.properties

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-7835.

Fix Version/s: 1.13.0
   Resolution: Fixed

> Correct doc typo of file name gfsecurity.properties
> ---
>
> Key: GEODE-7835
> URL: https://issues.apache.org/jira/browse/GEODE-7835
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
> Fix For: 1.13.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> File name gfsecurity.properties incorrectly contains a hyphen instead of a 
> period in this file:
> [https://geode.apache.org/docs/guide/111/tools_modules/pulse/pulse-auth.html]
> This ticket exists to correct that typo.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-7835) Correct doc typo of file name gfsecurity.properties

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller updated GEODE-7835:
---
Description: 
File name gfsecurity.properties incorrectly contains a hyphen instead of a 
period in this file:

[https://geode.apache.org/docs/guide/111/tools_modules/pulse/pulse-auth.html]

This ticket exists to correct that typo.

  was:
File name gfsecurity.properties incorectly contains a hyphen instead of a 
period in this file:

[https://geode.apache.org/docs/guide/111/tools_modules/pulse/pulse-auth.html]

This ticket exists to correct that typo.


> Correct doc typo of file name gfsecurity.properties
> ---
>
> Key: GEODE-7835
> URL: https://issues.apache.org/jira/browse/GEODE-7835
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> File name gfsecurity.properties incorrectly contains a hyphen instead of a 
> period in this file:
> [https://geode.apache.org/docs/guide/111/tools_modules/pulse/pulse-auth.html]
> This ticket exists to correct that typo.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-7835) Correct doc typo of file name gfsecurity.properties

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-7835:
--

Assignee: Karen Smoler Miller

> Correct doc typo of file name gfsecurity.properties
> ---
>
> Key: GEODE-7835
> URL: https://issues.apache.org/jira/browse/GEODE-7835
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> File name gfsecurity.properties incorectly contains a hyphen instead of a 
> period in this file:
> [https://geode.apache.org/docs/guide/111/tools_modules/pulse/pulse-auth.html]
> This ticket exists to correct that typo.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-7835) Correct doc typo of file name gfsecurity.properties

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-7835:
--

 Summary: Correct doc typo of file name gfsecurity.properties
 Key: GEODE-7835
 URL: https://issues.apache.org/jira/browse/GEODE-7835
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


File name gfsecurity.properties incorectly contains a hyphen instead of a 
period in this file:

[https://geode.apache.org/docs/guide/111/tools_modules/pulse/pulse-auth.html]

This ticket exists to correct that typo.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-7815) Document setting a GEODE_HOME env variable

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-7815.

Fix Version/s: 1.13.0
   Resolution: Fixed

> Document setting a GEODE_HOME env variable
> --
>
> Key: GEODE-7815
> URL: https://issues.apache.org/jira/browse/GEODE-7815
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
> Fix For: 1.13.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> While internal methods will check the classpath for locating WAR files, we 
> should document that setting a GEODE_HOME environment variable might an 
> easier method for some installations than changing the classpath.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-7815) Document setting a GEODE_HOME env variable

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-7815:
--

Assignee: Karen Smoler Miller

> Document setting a GEODE_HOME env variable
> --
>
> Key: GEODE-7815
> URL: https://issues.apache.org/jira/browse/GEODE-7815
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> While internal methods will check the classpath for locating WAR files, we 
> should document that setting a GEODE_HOME environment variable might an 
> easier method for some installations than changing the classpath.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-7815) Document setting a GEODE_HOME env variable

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-7815:
--

 Summary: Document setting a GEODE_HOME env variable
 Key: GEODE-7815
 URL: https://issues.apache.org/jira/browse/GEODE-7815
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


While internal methods will check the classpath for locating WAR files, we 
should document that setting a GEODE_HOME environment variable might an easier 
method for some installations than changing the classpath.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-7722) Aggregate function names are reserved words in OQL

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-7722:
--

 Summary: Aggregate function names are reserved words in OQL
 Key: GEODE-7722
 URL: https://issues.apache.org/jira/browse/GEODE-7722
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


See 
[https://geode.apache.org/docs/guide/111/developing/querying_basics/reserved_words.html].
  There are asterisks next to the aggregate function names.  

 

The prose for those words with asterisks is "The words with asterisk ({{*}}) 
after them are not currently used by Geode, but are reserved for future 
implementation."  I believe the future is here, as they are have been 
implemented in Apache Geode 1.11.

 

The task of this ticket is to update this page in the docs to remove the 
asterisk from all aggregate function names: MIN, MAX, COUNT, SUM, AVG, and 
GROUP BY.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-7212) User Guide - Authorization - update security permissions

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-7212.

Resolution: Fixed

DATA -> CLUSTER.

> User Guide - Authorization - update security permissions
> 
>
> Key: GEODE-7212
> URL: https://issues.apache.org/jira/browse/GEODE-7212
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Karen Smoler Miller
>Priority: Major
> Fix For: 1.12.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> "Fine-grained security" changes were implemented in v1.3, but docs & Wiki 
> were only recently updated. Pick up these changes in the user guide. See 
> [https://cwiki.apache.org/confluence/display/GEODE/Finer+grained+security].



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Reopened] (GEODE-7212) User Guide - Authorization - update security permissions

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reopened GEODE-7212:


The correct permission for CqQuery.stop() is CLUSTER:MANAGE:QUERY.  It was 
incorrectly changed to DATA:MANAGE:QUERY.

> User Guide - Authorization - update security permissions
> 
>
> Key: GEODE-7212
> URL: https://issues.apache.org/jira/browse/GEODE-7212
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Karen Smoler Miller
>Priority: Major
> Fix For: 1.12.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> "Fine-grained security" changes were implemented in v1.3, but docs & Wiki 
> were only recently updated. Pick up these changes in the user guide. See 
> [https://cwiki.apache.org/confluence/display/GEODE/Finer+grained+security].



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-7212) User Guide - Authorization - update security permissions

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-7212.

Fix Version/s: 1.12.0
   Resolution: Fixed

> User Guide - Authorization - update security permissions
> 
>
> Key: GEODE-7212
> URL: https://issues.apache.org/jira/browse/GEODE-7212
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Karen Smoler Miller
>Priority: Major
> Fix For: 1.12.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> "Fine-grained security" changes were implemented in v1.3, but docs & Wiki 
> were only recently updated. Pick up these changes in the user guide. See 
> [https://cwiki.apache.org/confluence/display/GEODE/Finer+grained+security].



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-7212) User Guide - Authorization - update security permissions

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-7212:
--

Assignee: Karen Smoler Miller

> User Guide - Authorization - update security permissions
> 
>
> Key: GEODE-7212
> URL: https://issues.apache.org/jira/browse/GEODE-7212
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Karen Smoler Miller
>Priority: Major
>
> "Fine-grained security" changes were implemented in v1.3, but docs & Wiki 
> were only recently updated. Pick up these changes in the user guide. See 
> [https://cwiki.apache.org/confluence/display/GEODE/Finer+grained+security].



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (GEODE-7430) Add 3 gfsh commands for JDBC driver to User Guide

[Karen Smoler Miller (Jira)]

[ 
https://issues.apache.org/jira/browse/GEODE-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16973829#comment-16973829
 ] 

Karen Smoler Miller edited comment on GEODE-7430 at 11/14/19 12:34 AM:
---

These 3 experimental commands are documented in the wiki.

*gfsh deregister driver*

{{gfsh>help deregister driver}}

{{NAME}}

{{    deregister driver }}

{{IS AVAILABLE}}

{{    true }}

{{SYNOPSIS}}

{{    (Experimental) Deregister a driver with the cluster's Driver Manager 
using}}

{{    the name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX }}

{{    deregister driver --driver-class=value }}

{{PARAMETERS }}

{{    driver-class }}

{{        The name of the driver class contained in a currently deployed jar to 
be }}

{{        deregistered with the cluster's Driver Manager. }}

{{        Required: true}}

*gfsh register driver*

{{gfsh>help register driver}}

{{NAME}}

{{    register driver}}

{{IS AVAILABLE}}

{{    true}}

{{SYNOPSIS}}

{{    (Experimental) Register a driver with the cluster's Driver Manager using 
the}}

{{    name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX}}

{{    register driver --driver-class=value}}

{{ PARAMETERS}}

{{    driver-class}}

{{        The name of the driver class contained in a currently deployed jar to 
be}}

{{        registered with the cluster's Driver Manager.}}

{{        Required: true}}

*gfsh list drivers*

{{gfsh>help list drivers}}

{{NAME}}

{{    list drivers}}

{{IS AVAILABLE}}

{{    true}}

{{SYNOPSIS}}

{{    (Experimental) Lists all drivers currently registered by the cluster's}}

{{    Driver Manager.}}

{{ SYNTAX}}

 {{   list drivers [--member-name=value]}}

{{PARAMETERS}}

{{    member-name}}

{{        Name of specific member to list drivers for.}}

{{        Required: false}}


was (Author: karensmolermiller):
These 3 experimental commands are documented in the wiki.

*gfsh deregister driver*

{{gfsh>help deregister driver}}

{{NAME}}

{{    deregister driver }}

{{IS AVAILABLE}}

{{    true }}

{{SYNOPSIS}}

{{    (Experimental) Deregister a driver with the cluster's Driver Manager 
using}}

{{    the name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX }}

{{    deregister driver --driver-class=value }}

{{PARAMETERS }}

{{    driver-class }}

{{        The name of the driver class contained in a currently deployed jar to 
be }}

{{        deregistered with the cluster's Driver Manager. }}

{{        Required: true}}

*gfsh register driver*

{{gfsh>help register driver}}

{{NAME}}

{{    register driver}}

{{IS AVAILABLE}}

{{    true}}

{{SYNOPSIS}}

{{    (Experimental) Register a driver with the cluster's Driver Manager using 
the}}

{{    name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX}}

{{    register driver --driver-class=value}}

{{ PARAMETERS}}

{{    driver-class}}

{{        The name of the driver class contained in a currently deployed jar to 
be}}

{{        registered with the cluster's Driver Manager.}}

{{        Required: true}}

*gfsh list drivers*

gfsh>help list drivers

{{NAME}}

    list drivers

{{IS AVAILABLE}}

    true

{{SYNOPSIS}}

{{    (Experimental) Lists all drivers currently registered by the cluster's}}

    Driver Manager.

{{ SYNTAX}}

    list drivers [--member-name=value]

PARAMETERS

    member-name

        Name of specific member to list drivers for.

        Required: false

> Add 3 gfsh commands for JDBC driver to User Guide
> -
>
> Key: GEODE-7430
> URL: https://issues.apache.org/jira/browse/GEODE-7430
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Karen Smoler Miller
>Priority: Major
>
> 3 commands were created and added to gfsh help, but didn't make it into the 
> manual.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (GEODE-7430) Add 3 gfsh commands for JDBC driver to User Guide

[Karen Smoler Miller (Jira)]

[ 
https://issues.apache.org/jira/browse/GEODE-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16973829#comment-16973829
 ] 

Karen Smoler Miller edited comment on GEODE-7430 at 11/14/19 12:33 AM:
---

These 3 experimental commands are documented in the wiki.

*gfsh deregister driver*

{{gfsh>help deregister driver}}

{{NAME}}

{{    deregister driver }}

{{IS AVAILABLE}}

{{    true }}

{{SYNOPSIS}}

{{    (Experimental) Deregister a driver with the cluster's Driver Manager 
using}}

{{    the name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX }}

{{    deregister driver --driver-class=value }}

{{PARAMETERS }}

{{    driver-class }}

{{        The name of the driver class contained in a currently deployed jar to 
be }}

{{        deregistered with the cluster's Driver Manager. }}

{{        Required: true}}

*gfsh register driver*

{{gfsh>help register driver}}

{{NAME}}

{{    register driver}}

{{IS AVAILABLE}}

{{    true}}

{{SYNOPSIS}}

{{    (Experimental) Register a driver with the cluster's Driver Manager using 
the}}

{{    name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX}}

{{    register driver --driver-class=value}}

{{ PARAMETERS}}

{{    driver-class}}

{{        The name of the driver class contained in a currently deployed jar to 
be}}

{{        registered with the cluster's Driver Manager.}}

{{        Required: true}}

*gfsh list drivers*

gfsh>help list drivers

{{NAME}}

    list drivers

{{IS AVAILABLE}}

    true

{{SYNOPSIS}}

{{    (Experimental) Lists all drivers currently registered by the cluster's}}

    Driver Manager.

{{ SYNTAX}}

    list drivers [--member-name=value]

PARAMETERS

    member-name

        Name of specific member to list drivers for.

        Required: false


was (Author: karensmolermiller):
These 3 experimental commands are documented in the wiki.

*gfsh deregister driver*

{{gfsh>help deregister driver}}

{{NAME}}

{{    deregister driver }}

{{IS AVAILABLE}}

{{    true }}

{{SYNOPSIS}}

{{    (Experimental) Deregister a driver with the cluster's Driver Manager 
using}}

{{    the name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX }}

{{    deregister driver --driver-class=value }}

{{PARAMETERS }}

{{    driver-class }}

{{        The name of the driver class contained in a currently deployed jar to 
be }}

{{        deregistered with the cluster's Driver Manager. }}

{{        Required: true}}

*gfsh register driver*

{{gfsh>help register driver}}

{{NAME}}

{{    register driver}}

{{IS AVAILABLE}}

{{    true}}

{{SYNOPSIS}}

{{    (Experimental) Register a driver with the cluster's Driver Manager using 
the}}

{{    name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX}}

{{    register driver --driver-class=value}}

{{ PARAMETERS}}

{{    driver-class}}

{{        The name of the driver class contained in a currently deployed jar to 
be}}

{{        registered with the cluster's Driver Manager.}}

{{        Required: true}}

*gfsh list drivers*

{{gfsh>help list drivers}}

{\{ NAME}}

{{    list drivers}}

{\{ IS AVAILABLE}}

{{    true}}

{\{ SYNOPSIS}}

{\{    (Experimental) Lists all drivers currently registered by the cluster's }}

{{    Driver Manager.}}

{\{ SYNTAX}}

{{    list drivers [--member-name=value]}}

{{PARAMETERS}}

{{    member-name}}

{{        Name of specific member to list drivers for.}}

{{        Required: false}}

> Add 3 gfsh commands for JDBC driver to User Guide
> -
>
> Key: GEODE-7430
> URL: https://issues.apache.org/jira/browse/GEODE-7430
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Karen Smoler Miller
>Priority: Major
>
> 3 commands were created and added to gfsh help, but didn't make it into the 
> manual.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (GEODE-7430) Add 3 gfsh commands for JDBC driver to User Guide

[Karen Smoler Miller (Jira)]

[ 
https://issues.apache.org/jira/browse/GEODE-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16973829#comment-16973829
 ] 

Karen Smoler Miller edited comment on GEODE-7430 at 11/14/19 12:32 AM:
---

These 3 experimental commands are documented in the wiki.

*gfsh deregister driver*

{{gfsh>help deregister driver}}

{{NAME}}

{{    deregister driver }}

{{IS AVAILABLE}}

{{    true }}

{{SYNOPSIS}}

{{    (Experimental) Deregister a driver with the cluster's Driver Manager 
using}}

{{    the name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX }}

{{    deregister driver --driver-class=value }}

{{PARAMETERS }}

{{    driver-class }}

{{        The name of the driver class contained in a currently deployed jar to 
be }}

{{        deregistered with the cluster's Driver Manager. }}

{{        Required: true}}

*gfsh register driver*

{{gfsh>help register driver}}

{{NAME}}

{{    register driver}}

{{IS AVAILABLE}}

{{    true}}

{{SYNOPSIS}}

{{    (Experimental) Register a driver with the cluster's Driver Manager using 
the}}

{{    name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX}}

{{    register driver --driver-class=value}}

{{ PARAMETERS}}

{{    driver-class}}

{{        The name of the driver class contained in a currently deployed jar to 
be}}

{{        registered with the cluster's Driver Manager.}}

{{        Required: true}}

*gfsh list drivers*

{{gfsh>help list drivers}}

{\{ NAME}}

{{    list drivers}}

{\{ IS AVAILABLE}}

{{    true}}

{\{ SYNOPSIS}}

{\{    (Experimental) Lists all drivers currently registered by the cluster's }}

{{    Driver Manager.}}

{\{ SYNTAX}}

{{    list drivers [--member-name=value]}}

{{PARAMETERS}}

{{    member-name}}

{{        Name of specific member to list drivers for.}}

{{        Required: false}}


was (Author: karensmolermiller):
These 3 experimental commands are documented in the wiki.

*gfsh deregister driver*

{{gfsh>help deregister driver}}

{{NAME}}

{{    deregister driver }}

{{IS AVAILABLE}}

{{    true }}

{{SYNOPSIS}}

{{    (Experimental) Deregister a driver with the cluster's Driver Manager 
using}}

{{    the name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX }}

{{    deregister driver --driver-class=value }}

{{PARAMETERS }}

{{    driver-class }}

{{        The name of the driver class contained in a currently deployed jar to 
be }}

{{        deregistered with the cluster's Driver Manager. }}

{{        Required: true}}

*gfsh register driver*

{{gfsh>help register driver}}

{{NAME}}

    register driver

{{IS AVAILABLE}}

    true

{{SYNOPSIS}}

{{    (Experimental) Register a driver with the cluster's Driver Manager using 
the}}

{{    name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX}}

    register driver --driver-class=value

{{ PARAMETERS}}

    driver-class

        The name of the driver class contained in a currently deployed jar 
to be

        registered with the cluster's Driver Manager.

        Required: true

*gfsh list drivers*

{{gfsh>help list drivers}}

{\{ NAME}}

{{    list drivers}}

{\{ IS AVAILABLE}}

{{    true}}

{\{ SYNOPSIS}}

{\{    (Experimental) Lists all drivers currently registered by the cluster's }}

{{    Driver Manager.}}

{\{ SYNTAX}}

{{    list drivers [--member-name=value]}}

{{PARAMETERS}}

{{    member-name}}

{{        Name of specific member to list drivers for.}}

{{        Required: false}}

> Add 3 gfsh commands for JDBC driver to User Guide
> -
>
> Key: GEODE-7430
> URL: https://issues.apache.org/jira/browse/GEODE-7430
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Karen Smoler Miller
>Priority: Major
>
> 3 commands were created and added to gfsh help, but didn't make it into the 
> manual.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (GEODE-7430) Add 3 gfsh commands for JDBC driver to User Guide

[Karen Smoler Miller (Jira)]

[ 
https://issues.apache.org/jira/browse/GEODE-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16973829#comment-16973829
 ] 

Karen Smoler Miller edited comment on GEODE-7430 at 11/14/19 12:31 AM:
---

These 3 experimental commands are documented in the wiki.

*gfsh deregister driver*

{{gfsh>help deregister driver}}

{{NAME}}

{{    deregister driver }}

{{IS AVAILABLE}}

{{    true }}

{{SYNOPSIS}}

{{    (Experimental) Deregister a driver with the cluster's Driver Manager 
using}}

{{    the name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX }}

{{    deregister driver --driver-class=value }}

{{PARAMETERS }}

{{    driver-class }}

{{        The name of the driver class contained in a currently deployed jar to 
be }}

{{        deregistered with the cluster's Driver Manager. }}

{{        Required: true}}

*gfsh register driver*

{{gfsh>help register driver}}

{{NAME}}

    register driver

{{IS AVAILABLE}}

    true

{{SYNOPSIS}}

{{    (Experimental) Register a driver with the cluster's Driver Manager using 
the}}

{{    name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX}}

    register driver --driver-class=value

{{ PARAMETERS}}

    driver-class

        The name of the driver class contained in a currently deployed jar 
to be

        registered with the cluster's Driver Manager.

        Required: true

*gfsh list drivers*

{{gfsh>help list drivers}}

{\{ NAME}}

{{    list drivers}}

{\{ IS AVAILABLE}}

{{    true}}

{\{ SYNOPSIS}}

{\{    (Experimental) Lists all drivers currently registered by the cluster's }}

{{    Driver Manager.}}

{\{ SYNTAX}}

{{    list drivers [--member-name=value]}}

{{PARAMETERS}}

{{    member-name}}

{{        Name of specific member to list drivers for.}}

{{        Required: false}}


was (Author: karensmolermiller):
These 3 experimental commands are documented in the wiki.

*gfsh deregister driver*

{{gfsh>help deregister driver}}

{{NAME}}

{{    deregister driver }}

{{IS AVAILABLE}}

{{    true }}

{{SYNOPSIS}}

{{    (Experimental) Deregister a driver with the cluster's Driver Manager 
using}}

{{    the name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX }}

{{    deregister driver --driver-class=value }}

{{PARAMETERS }}

{{    driver-class }}

{{        The name of the driver class contained in a currently deployed jar to 
be }}

{{        deregistered with the cluster's Driver Manager. }}

{{        Required: true}}

*gfsh register driver*

{\{gfsh>help register driver }}

{\{NAME }}

{{    register driver}}

{\{ IS AVAILABLE}}

{{    true}}

{\{ SYNOPSIS}}

{\{    (Experimental) Register a driver with the cluster's Driver Manager using 
the }}

{\{    name of a driver class contained within a currenly deployed jar. }}

{\{SYNTAX }}

{{    register driver --driver-class=value}}

{\{ PARAMETERS}}

{{    driver-class}}

{{        The name of the driver class contained in a currently deployed jar to 
be}}

{{        registered with the cluster's Driver Manager.}}

{{        Required: true}}

*gfsh list drivers*

{{gfsh>help list drivers}}

{\{ NAME}}

{{    list drivers}}

{\{ IS AVAILABLE}}

{{    true}}

{\{ SYNOPSIS}}

{\{    (Experimental) Lists all drivers currently registered by the cluster's }}

{{    Driver Manager.}}

{\{ SYNTAX}}

{{    list drivers [--member-name=value]}}

{{PARAMETERS}}

{{    member-name}}

{{        Name of specific member to list drivers for.}}

{{        Required: false}}

> Add 3 gfsh commands for JDBC driver to User Guide
> -
>
> Key: GEODE-7430
> URL: https://issues.apache.org/jira/browse/GEODE-7430
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Karen Smoler Miller
>Priority: Major
>
> 3 commands were created and added to gfsh help, but didn't make it into the 
> manual.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (GEODE-7430) Add 3 gfsh commands for JDBC driver to User Guide

[Karen Smoler Miller (Jira)]

[ 
https://issues.apache.org/jira/browse/GEODE-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16973829#comment-16973829
 ] 

Karen Smoler Miller edited comment on GEODE-7430 at 11/14/19 12:30 AM:
---

These 3 experimental commands are documented in the wiki.

*gfsh deregister driver*

{{gfsh>help deregister driver}}

{{NAME}}

{{    deregister driver }}

{{IS AVAILABLE}}

{{    true }}

{{SYNOPSIS}}

{{    (Experimental) Deregister a driver with the cluster's Driver Manager 
using}}

{{    the name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX }}

{{    deregister driver --driver-class=value }}

{{PARAMETERS }}

{{    driver-class }}

{{        The name of the driver class contained in a currently deployed jar to 
be }}

{{        deregistered with the cluster's Driver Manager. }}

{{        Required: true}}

*gfsh register driver*

{\{gfsh>help register driver }}

{\{NAME }}

{{    register driver}}

{\{ IS AVAILABLE}}

{{    true}}

{\{ SYNOPSIS}}

{\{    (Experimental) Register a driver with the cluster's Driver Manager using 
the }}

{\{    name of a driver class contained within a currenly deployed jar. }}

{\{SYNTAX }}

{{    register driver --driver-class=value}}

{\{ PARAMETERS}}

{{    driver-class}}

{{        The name of the driver class contained in a currently deployed jar to 
be}}

{{        registered with the cluster's Driver Manager.}}

{{        Required: true}}

*gfsh list drivers*

{{gfsh>help list drivers}}

{\{ NAME}}

{{    list drivers}}

{\{ IS AVAILABLE}}

{{    true}}

{\{ SYNOPSIS}}

{\{    (Experimental) Lists all drivers currently registered by the cluster's }}

{{    Driver Manager.}}

{\{ SYNTAX}}

{{    list drivers [--member-name=value]}}

{{PARAMETERS}}

{{    member-name}}

{{        Name of specific member to list drivers for.}}

{{        Required: false}}


was (Author: karensmolermiller):
These 3 experimental commands are documented in the wiki.

*gfsh deregister driver*

{{gfsh>help deregister driver}}

{{NAME}}

{{    deregister driver }}

IS AVAILABLE

{{    true }}

SYNOPSIS

    (Experimental) Deregister a driver with the cluster's Driver Manager 
using

{{    the name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX }}

{{    deregister driver --driver-class=value }}

{{PARAMETERS }}

{{    driver-class }}

{{        The name of the driver class contained in a currently deployed jar to 
be }}

{{        deregistered with the cluster's Driver Manager. }}

        Required: true

*gfsh register driver*

{\{gfsh>help register driver }}

{\{NAME }}

{{    register driver}}

{\{ IS AVAILABLE}}

{{    true}}

{\{ SYNOPSIS}}

{\{    (Experimental) Register a driver with the cluster's Driver Manager using 
the }}

{\{    name of a driver class contained within a currenly deployed jar. }}

{\{SYNTAX }}

{{    register driver --driver-class=value}}

{\{ PARAMETERS}}

{{    driver-class}}

{{        The name of the driver class contained in a currently deployed jar to 
be}}

{{        registered with the cluster's Driver Manager.}}

{{        Required: true}}

*gfsh list drivers*

{{gfsh>help list drivers}}

{\{ NAME}}

{{    list drivers}}

{\{ IS AVAILABLE}}

{{    true}}

{\{ SYNOPSIS}}

{\{    (Experimental) Lists all drivers currently registered by the cluster's }}

{{    Driver Manager.}}

{\{ SYNTAX}}

{{    list drivers [--member-name=value]}}

{{PARAMETERS}}

{{    member-name}}

{{        Name of specific member to list drivers for.}}

{{        Required: false}}

> Add 3 gfsh commands for JDBC driver to User Guide
> -
>
> Key: GEODE-7430
> URL: https://issues.apache.org/jira/browse/GEODE-7430
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Karen Smoler Miller
>Priority: Major
>
> 3 commands were created and added to gfsh help, but didn't make it into the 
> manual.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (GEODE-7430) Add 3 gfsh commands for JDBC driver to User Guide

[Karen Smoler Miller (Jira)]

[ 
https://issues.apache.org/jira/browse/GEODE-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16973829#comment-16973829
 ] 

Karen Smoler Miller edited comment on GEODE-7430 at 11/14/19 12:29 AM:
---

These 3 experimental commands are documented in the wiki.

*gfsh deregister driver*

{{gfsh>help deregister driver}}

{{NAME}}

{{    deregister driver }}

IS AVAILABLE

{{    true }}

SYNOPSIS

    (Experimental) Deregister a driver with the cluster's Driver Manager 
using

{{    the name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX }}

{{    deregister driver --driver-class=value }}

{{PARAMETERS }}

{{    driver-class }}

{{        The name of the driver class contained in a currently deployed jar to 
be }}

{{        deregistered with the cluster's Driver Manager. }}

        Required: true

*gfsh register driver*

{\{gfsh>help register driver }}

{\{NAME }}

{{    register driver}}

{\{ IS AVAILABLE}}

{{    true}}

{\{ SYNOPSIS}}

{\{    (Experimental) Register a driver with the cluster's Driver Manager using 
the }}

{\{    name of a driver class contained within a currenly deployed jar. }}

{\{SYNTAX }}

{{    register driver --driver-class=value}}

{\{ PARAMETERS}}

{{    driver-class}}

{{        The name of the driver class contained in a currently deployed jar to 
be}}

{{        registered with the cluster's Driver Manager.}}

{{        Required: true}}

*gfsh list drivers*

{{gfsh>help list drivers}}

{\{ NAME}}

{{    list drivers}}

{\{ IS AVAILABLE}}

{{    true}}

{\{ SYNOPSIS}}

{\{    (Experimental) Lists all drivers currently registered by the cluster's }}

{{    Driver Manager.}}

{\{ SYNTAX}}

{{    list drivers [--member-name=value]}}

{{PARAMETERS}}

{{    member-name}}

{{        Name of specific member to list drivers for.}}

{{        Required: false}}


was (Author: karensmolermiller):
These 3 experimental commands are documented in the wiki.

*gfsh deregister driver*

{{gfsh>help deregister driver }}

{{NAME }}

{{    deregister driver }}

{{IS AVAILABLE}}

{{    true }}

{{SYNOPSIS}}

{{    (Experimental) Deregister a driver with the cluster's Driver Manager 
using}}

{{    the name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX }}

{{    deregister driver --driver-class=value }}

{{PARAMETERS }}

{{    driver-class }}

{{        The name of the driver class contained in a currently deployed jar to 
be }}

{{        deregistered with the cluster's Driver Manager. }}

{{        Required: true}}

*gfsh register driver*

{{gfsh>help register driver }}

{{NAME }}

{{    register driver}}

{{ IS AVAILABLE}}

{{    true}}

{{ SYNOPSIS}}

{{    (Experimental) Register a driver with the cluster's Driver Manager using 
the }}

{{    name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX }}

{{    register driver --driver-class=value}}

{{ PARAMETERS}}

{{    driver-class}}

{{        The name of the driver class contained in a currently deployed jar to 
be}}

{{        registered with the cluster's Driver Manager.}}

{{        Required: true}}

*gfsh list drivers*

{{gfsh>help list drivers}}

{{ NAME}}

{{    list drivers}}

{{ IS AVAILABLE}}

{{    true}}

{{ SYNOPSIS}}

{{    (Experimental) Lists all drivers currently registered by the cluster's }}

{{    Driver Manager.}}

{{ SYNTAX}}

{{    list drivers [--member-name=value]}}

{{PARAMETERS}}

{{    member-name}}

{{        Name of specific member to list drivers for.}}

{{        Required: false}}

> Add 3 gfsh commands for JDBC driver to User Guide
> -
>
> Key: GEODE-7430
> URL: https://issues.apache.org/jira/browse/GEODE-7430
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Karen Smoler Miller
>Priority: Major
>
> 3 commands were created and added to gfsh help, but didn't make it into the 
> manual.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (GEODE-7430) Add 3 gfsh commands for JDBC driver to User Guide

[Karen Smoler Miller (Jira)]

[ 
https://issues.apache.org/jira/browse/GEODE-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16973829#comment-16973829
 ] 

Karen Smoler Miller commented on GEODE-7430:


These 3 experimental commands are documented in the wiki.

*gfsh deregister driver*

{{gfsh>help deregister driver }}

{{NAME }}

{{    deregister driver }}

{{IS AVAILABLE}}

{{    true }}

{{SYNOPSIS}}

{{    (Experimental) Deregister a driver with the cluster's Driver Manager 
using}}

{{    the name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX }}

{{    deregister driver --driver-class=value }}

{{PARAMETERS }}

{{    driver-class }}

{{        The name of the driver class contained in a currently deployed jar to 
be }}

{{        deregistered with the cluster's Driver Manager. }}

{{        Required: true}}

*gfsh register driver*

{{gfsh>help register driver }}

{{NAME }}

{{    register driver}}

{{ IS AVAILABLE}}

{{    true}}

{{ SYNOPSIS}}

{{    (Experimental) Register a driver with the cluster's Driver Manager using 
the }}

{{    name of a driver class contained within a currenly deployed jar. }}

{{SYNTAX }}

{{    register driver --driver-class=value}}

{{ PARAMETERS}}

{{    driver-class}}

{{        The name of the driver class contained in a currently deployed jar to 
be}}

{{        registered with the cluster's Driver Manager.}}

{{        Required: true}}

*gfsh list drivers*

{{gfsh>help list drivers}}

{{ NAME}}

{{    list drivers}}

{{ IS AVAILABLE}}

{{    true}}

{{ SYNOPSIS}}

{{    (Experimental) Lists all drivers currently registered by the cluster's }}

{{    Driver Manager.}}

{{ SYNTAX}}

{{    list drivers [--member-name=value]}}

{{PARAMETERS}}

{{    member-name}}

{{        Name of specific member to list drivers for.}}

{{        Required: false}}

> Add 3 gfsh commands for JDBC driver to User Guide
> -
>
> Key: GEODE-7430
> URL: https://issues.apache.org/jira/browse/GEODE-7430
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Karen Smoler Miller
>Priority: Major
>
> 3 commands were created and added to gfsh help, but didn't make it into the 
> manual.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-7430) Add 3 gfsh commands for JDBC driver to User Guide

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-7430:
--

Assignee: Karen Smoler Miller

> Add 3 gfsh commands for JDBC driver to User Guide
> -
>
> Key: GEODE-7430
> URL: https://issues.apache.org/jira/browse/GEODE-7430
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Karen Smoler Miller
>Priority: Major
>
> 3 commands were created and added to gfsh help, but didn't make it into the 
> manual.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-7331) Improve docs on logging (with optional Log4j)

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-7331.

Fix Version/s: 1.11.0
   Resolution: Fixed

> Improve docs on logging (with optional Log4j)
> -
>
> Key: GEODE-7331
> URL: https://issues.apache.org/jira/browse/GEODE-7331
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
> Fix For: 1.11.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Log4j is in its own module.  Update the docs to reflect changes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-7332) Add OQL Aggregates link in docs

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-7332.

Fix Version/s: 1.11.0
 Assignee: Karen Smoler Miller
   Resolution: Fixed

> Add OQL Aggregates link in docs
> ---
>
> Key: GEODE-7332
> URL: https://issues.apache.org/jira/browse/GEODE-7332
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
> Fix For: 1.11.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Small change, but useful. File 
> developing/querying_basics/what_is_a_query_string.html has a list of useful 
> query string building blocks.  Add a link to the descriptions of the OQL 
> aggregates to the list.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-7332) Add OQL Aggregates link in docs

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-7332:
--

 Summary: Add OQL Aggregates link in docs
 Key: GEODE-7332
 URL: https://issues.apache.org/jira/browse/GEODE-7332
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


Small change, but useful. File 
developing/querying_basics/what_is_a_query_string.html has a list of useful 
query string building blocks.  Add a link to the descriptions of the OQL 
aggregates to the list.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-7331) Improve docs on logging (with optional Log4j)

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-7331:
--

Assignee: Karen Smoler Miller

> Improve docs on logging (with optional Log4j)
> -
>
> Key: GEODE-7331
> URL: https://issues.apache.org/jira/browse/GEODE-7331
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> Log4j is in its own module.  Update the docs to reflect changes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-7331) Improve docs on logging (with optional Log4j)

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-7331:
--

 Summary: Improve docs on logging (with optional Log4j)
 Key: GEODE-7331
 URL: https://issues.apache.org/jira/browse/GEODE-7331
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


Log4j is in its own module.  Update the docs to reflect changes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-7329) Document how to configure logging other than Log4j

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-7329:
--

 Summary: Document how to configure logging other than Log4j
 Key: GEODE-7329
 URL: https://issues.apache.org/jira/browse/GEODE-7329
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


Now that Log4j is in its own module, users can configure their own non-Log4j 
logging system. We should tell users how to configure this.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-7192) Update cluster config behavior in documentation

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-7192.

Fix Version/s: 1.11.0
   Resolution: Fixed

> Update cluster config behavior in documentation
> ---
>
> Key: GEODE-7192
> URL: https://issues.apache.org/jira/browse/GEODE-7192
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Joey McAllister
>Assignee: Karen Smoler Miller
>Priority: Minor
> Fix For: 1.11.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The [Cluster Configuration Files and Troubleshooting 
> page|[https://geode.apache.org/docs/guide/19/configuring/cluster_config/gfsh_config_troubleshooting.html]]
>  currently describes older Geode behavior regarding the cluster.xml file. 
> According to [~jinmeiliao], now "the xml/properties files are kept in a 
> persisted region. It’s not in the file system anymore; only jar files are 
> saved in the file system. When using `export cluster-config` command, it can 
> print the content on the screen for you to look at."
> This page should be updated to reflect the current behavior.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-7192) Update cluster config behavior in documentation

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-7192:
--

Assignee: Karen Smoler Miller

> Update cluster config behavior in documentation
> ---
>
> Key: GEODE-7192
> URL: https://issues.apache.org/jira/browse/GEODE-7192
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Joey McAllister
>Assignee: Karen Smoler Miller
>Priority: Minor
>
> The [Cluster Configuration Files and Troubleshooting 
> page|[https://geode.apache.org/docs/guide/19/configuring/cluster_config/gfsh_config_troubleshooting.html]]
>  currently describes older Geode behavior regarding the cluster.xml file. 
> According to [~jinmeiliao], now "the xml/properties files are kept in a 
> persisted region. It’s not in the file system anymore; only jar files are 
> saved in the file system. When using `export cluster-config` command, it can 
> print the content on the screen for you to look at."
> This page should be updated to reflect the current behavior.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-7280) Clarify docs: DELETE V1 endpoint only for replicated regions

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-7280.

Fix Version/s: 1.11.0
   Resolution: Fixed

> Clarify docs: DELETE V1 endpoint only for replicated regions
> 
>
> Key: GEODE-7280
> URL: https://issues.apache.org/jira/browse/GEODE-7280
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
> Fix For: 1.11.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The DELETE REST endpoint  for removing all entries only works for replicated 
> (not partitioned) regions.  This should be explicit within the documentation.
> Here are two places (in the Geode 1.10 docs) that should identify that 
> restriction:
>  * reference: 
> [https://geode.apache.org/docs/guide/110/rest_apps/delete_all_data.html]
>  * 
> [https://geode.apache.org/docs/guide/110/rest_apps/develop_rest_apps.html#topic_qhs_f25_m4],
>  in the subsection titled Deleting Region Data



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-7280) Clarify docs: DELETE V1 endpoint only for replicated regions

[Karen Smoler Miller (Jira)]

Karen Smoler Miller created GEODE-7280:
--

 Summary: Clarify docs: DELETE V1 endpoint only for replicated 
regions
 Key: GEODE-7280
 URL: https://issues.apache.org/jira/browse/GEODE-7280
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


The DELETE REST endpoint  for removing all entries only works for replicated 
(not partitioned) regions.  This should be explicit within the documentation.

Here are two places (in the Geode 1.10 docs) that should identify that 
restriction:
 * reference: 
[https://geode.apache.org/docs/guide/110/rest_apps/delete_all_data.html]
 * 
[https://geode.apache.org/docs/guide/110/rest_apps/develop_rest_apps.html#topic_qhs_f25_m4],
 in the subsection titled Deleting Region Data



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-7280) Clarify docs: DELETE V1 endpoint only for replicated regions

[Karen Smoler Miller (Jira)]

 [ 
https://issues.apache.org/jira/browse/GEODE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-7280:
--

Assignee: Karen Smoler Miller

> Clarify docs: DELETE V1 endpoint only for replicated regions
> 
>
> Key: GEODE-7280
> URL: https://issues.apache.org/jira/browse/GEODE-7280
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> The DELETE REST endpoint  for removing all entries only works for replicated 
> (not partitioned) regions.  This should be explicit within the documentation.
> Here are two places (in the Geode 1.10 docs) that should identify that 
> restriction:
>  * reference: 
> [https://geode.apache.org/docs/guide/110/rest_apps/delete_all_data.html]
>  * 
> [https://geode.apache.org/docs/guide/110/rest_apps/develop_rest_apps.html#topic_qhs_f25_m4],
>  in the subsection titled Deleting Region Data



--
This message was sent by Atlassian Jira
(v8.3.4#803005)