[ 
https://issues.apache.org/jira/browse/STORM-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167798#comment-15167798
 ] 

ASF GitHub Bot commented on STORM-1542:
---------------------------------------

Github user kishorvpatil commented on the pull request:

    https://github.com/apache/storm/pull/1138#issuecomment-188963245
  
    LGTM. +1. 



> Taking jstack for a worker in UI results in endless empty jstack dumps
> ----------------------------------------------------------------------
>
>                 Key: STORM-1542
>                 URL: https://issues.apache.org/jira/browse/STORM-1542
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-core
>    Affects Versions: 1.0.0
>            Reporter: Abhishek Agarwal
>            Assignee: Abhishek Agarwal
>            Priority: Critical
>
> Resolved path for jstack command on supervisor is
> /home/y/share/yjava_jdk/java/jstack which doesn't exist. command returns 127 
> as exit code. When a request for jstack dump is made from UI, a zookeeper 
> node is created. Now supervisor keeps on reading this node, executes jstack 
> command and since exit code is non-zero, doesn't delete the node afterwards. 
> Thus supervisor keeps on executing the command forever and each invocation 
> creates an new empty file.
> {noformat}
> $BINPATH/jstack $1 > "$2/${FILENAME}"
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to