[
https://issues.apache.org/jira/browse/OOZIE-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664048#comment-13664048
]
Rohini Palaniswamy commented on OOZIE-1388:
-------------------------------------------
jstack gives thread information and tool like jvmtop gives thread usage
information but requires logging into a production Oozie server instance.
jconsole or jvisualvm cannot be used to connect the Oozie server as the server
is not launched with -Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false.
Found it very hard to debug a high CPU utilization scenario (600-800% on 16
core) in production under heavy load. By the time I managed to find jvmtop
(before deciding to write code myself to dump ThreadMXBean from the server as
local attaching to jvm process and fetching JMX metrics is possible without any
configuration), the CPU usage had gone down. A servlet would have saved lot of
time.
> Add a admin servlet to show thread stack trace and CPU usage per thread
> -----------------------------------------------------------------------
>
> Key: OOZIE-1388
> URL: https://issues.apache.org/jira/browse/OOZIE-1388
> Project: Oozie
> Issue Type: Improvement
> Reporter: Rohini Palaniswamy
> Assignee: Rohini Palaniswamy
>
> ThreadMXBean can be used to display the stack trace and also CPU usage per
> thread. The servlet will be very useful for debugging.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
