[
https://issues.apache.org/jira/browse/STORM-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151245#comment-15151245
]
Kishor Patil commented on STORM-1542:
-------------------------------------
[~abhishek.agarwal] It looks like a good option to turn this into a synchronous
mode. I would be watchful during implementation
- for multitenant, these operations needs to be launched as user.
- the heap-dump like actions in synchronous mode could take long time - due to
heapsize and + time to download dump results back to browser in synchronous
mode.
Currently, supervisor relaunches the profiler ( in case of worker restarts..)
but that feature would seize to exist ( as supervisor uses ZK to remember
launching profilers for that worker)
The idea otherwise sounds good.
> 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)
