[
https://issues.apache.org/jira/browse/GEODE-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17279884#comment-17279884
]
ASF GitHub Bot commented on GEODE-8917:
---------------------------------------
karensmolermiller opened a new pull request #6009:
URL: https://github.com/apache/geode/pull/6009
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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)
