Harsh J created BIGTOP-1061:
-------------------------------
Summary: Provide a jstack capturing script
Key: BIGTOP-1061
URL: https://issues.apache.org/jira/browse/BIGTOP-1061
Project: Bigtop
Issue Type: New Feature
Affects Versions: 0.7.0
Reporter: Harsh J
Priority: Minor
To grab a jstack, a common thing maintaining people and devs equally do, we
currently have to do a 3-step process:
1. Know which user to run the jstack as (hbase, hdfs, mapred, etc.)
2. Grab the PID using a tool (ps, jps, etc.)
3. Run jstack with the right JAVA_HOME path, cause some systems don't have its
bin on the PATH.
I feel we could make Bigtop improve this process of debug-material collection,
mainly jstack first. Bigtop service scripts and env-files know the right user
behind a daemon, Bigtop service scripts have access to the PID, and Bigtop also
uses JVM path detection. Perhaps we could add something like '{{service
hadoop-hdfs-namenode jstack}}' to grab a NameNode jstack as the right user with
the right PID, and drop it into the configured log location.
--
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
