[
https://issues.apache.org/jira/browse/OOZIE-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Sasvari updated OOZIE-2296:
----------------------------------
Attachment: OOZIE-2296-001.patch
[~rkanter] I tested your patch and made a minor modification in
{{saveThreadDumpPage}} to use the proper API call to get JVM info (sending
request to {{OOZIE_BASE_URL/admin/jvminfo.jsp}} instead of
{{OOZIE_BASE_URL//admin/jvminfo.jsp}}).
Example run:
{code}
$ bin/oozie-diag-bundle-collector.sh -jobs
0000001-170918144116149-oozie-asas-W -oozie http://localhost:11000/oozie
-output .
Using Temporary Directory:
/var/folders/9q/f8p_r6gj0wbck49_dc092q_m0000gp/T/1505741327859-0
Getting Sharelib Information...Done
Getting Configuration...Done
Getting OS Environment Variables...Done
Getting Java System Properties...Done
Getting Instrumentation...Done
Getting Metrics...Skipping (Metrics are unavailable)
Getting Queue Dump...Done
Getting Thread Dump...Done
Getting Details for 0000001-170918144116149-oozie-asas-W...Done
Creating Zip File:
/Users/asasvari/workspace/apache/oozie_dup/distro/target/oozie-5.0.0-SNAPSHOT-distro/oozie-5.0.0-SNAPSHOT/./oozie-diag-bundle-1505741328389.zip...Done
$ unzip -l
/Users/asasvari/workspace/apache/oozie_dup/distro/target/oozie-5.0.0-SNAPSHOT-distro/oozie-5.0.0-SNAPSHOT/./oozie-diag-bundle-1505748797206.zip
Archive:
/Users/asasvari/workspace/apache/oozie_dup/distro/target/oozie-5.0.0-SNAPSHOT-distro/oozie-5.0.0-SNAPSHOT/./oozie-diag-bundle-1505748797206.zip
Length Date Time Name
-------- ---- ---- ----
2574 09-18-17 17:33 /0000001-170918144116149-oozie-asas-W/info.txt
308 09-18-17 17:33 /0000001-170918144116149-oozie-asas-W/job.properties
6808 09-18-17 17:33 /0000001-170918144116149-oozie-asas-W/log.txt
0 09-18-17 17:33
/0000001-170918144116149-oozie-asas-W/resolved-actions/
2045 09-18-17 17:33
/0000001-170918144116149-oozie-asas-W/resolved-actions/mr-node.xml
2559 09-18-17 17:33 /0000001-170918144116149-oozie-asas-W/workflow.xml
64567 09-18-17 17:33 /effective-oozie-site.xml
27462 09-18-17 17:33 /instrumentation.txt
32359 09-18-17 17:33 /java-sys-props.txt
3557 09-18-17 17:33 /os-env-vars.txt
279 09-18-17 17:33 /queue-dump.txt
38906 09-18-17 17:33 /sharelib.txt
102263 09-18-17 17:33 /thread-dump.html
-------- -------
283687 13 files
{code}
Tests and documentation are still missing.
> Add an Oozie diagnostic bundle tool
> -----------------------------------
>
> Key: OOZIE-2296
> URL: https://issues.apache.org/jira/browse/OOZIE-2296
> Project: Oozie
> Issue Type: New Feature
> Components: tools
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Attachments: OOZIE-2296-001.patch
>
>
> To help with our support cases, I've built a tool that collects a bunch of
> job and other information from Oozie that throws it all in a tarball. The
> idea is that the user can just click a button in Cloudera Manager, and it
> will run this tool.
> This tool could be useful for others as an easy way to get information out of
> Oozie, so I thought I'd contribute it here. It's built as a "tool" (so it
> sits next to the sharelib and database tools), and simply uses the Oozie
> client for getting pretty much everything, so it doesn't require anything
> special.
> Here's the information that it can get:
> # Sharelib: {{ooze admin -shareliblist}} and {{oozie admin -shareliblist
> <foo>}}
> # Oozie Server's resolved loaded configuration (from admin endpoint)
> # Other admin commands output (queue dump, env vars, etc)
> # Thread dump (HOST:11000/oozie/admin/jvminfo.jsp)
> # Details from last n jobs and/or specific list of jobs
> #- job.properties contents
> #- XML definition
> #- verbose status for each job and each action etc
> #- Oozie logs
> #- Unfortunately, we can't get the launcher jobs' logs from Hadoop
> # Metrics/Instrumentation
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
