[
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)
