[
https://issues.apache.org/jira/browse/STORM-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15145882#comment-15145882
]
Abhishek Agarwal commented on STORM-1542:
-----------------------------------------
was pondering over this and logviewer seems like the right place to do worker
profiling/debugging. logviewer can be used as an admin tool to take thread
stacks, heap dumps etc. There is no need to configure additional ports on
supervisor, worker etc. zookeeper need not be used at all for debugging.
Debugging requests can be served inline synchronously rather than through files
on system.
[~ptgoetz] [~revans2] Fix for debugging/profiling is an important part of 1.0
stabilization. If the approach mentioned above sounds good, I can put up a
patch for this.
> 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)
