[ https://issues.apache.org/jira/browse/GEODE-8916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17279195#comment-17279195 ]
ASF subversion and git services commented on GEODE-8916: -------------------------------------------------------- Commit bbf01a40d0000b6ed061a5c265a132244f39da10 in geode's branch refs/heads/feature/GEODE-8916 from Barry Oglesby [ https://gitbox.apache.org/repos/asf?p=geode.git;h=bbf01a4 ] GEODE-8916: Updated junit test > 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)<v1>:41000 > gemfire-cluster-locator-0 | > xx.xx.x.xxx(gemfire-cluster-locator-0:1:locator)<ec><v0>:41000 [Coordinator] > gemfire-cluster-server-1 | xx.xx.x.xxx(gemfire-cluster-server-1:1)<v2>: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)