[ https://issues.apache.org/jira/browse/OOZIE-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239322#comment-16239322 ]
Attila Sasvari commented on OOZIE-2296: --------------------------------------- Generated bundle is as follows: {code} 2741 11-05-17 00:28 /0000000-171105002642017-oozie-asas-W/info.txt 307 11-05-17 00:28 /0000000-171105002642017-oozie-asas-W/job.properties 8477 11-05-17 00:28 /0000000-171105002642017-oozie-asas-W/log.txt 0 11-05-17 00:28 /0000000-171105002642017-oozie-asas-W/resolved-actions/ 0 11-05-17 00:28 /0000000-171105002642017-oozie-asas-W/resolved-actions/:start:.xml 0 11-05-17 00:28 /0000000-171105002642017-oozie-asas-W/resolved-actions/end.xml 83709 11-05-17 00:28 /0000000-171105002642017-oozie-asas-W/resolved-actions/launcher_mr-node.log 2045 11-05-17 00:28 /0000000-171105002642017-oozie-asas-W/resolved-actions/mr-node.xml 2559 11-05-17 00:28 /0000000-171105002642017-oozie-asas-W/workflow.xml 66586 11-05-17 00:28 /effective-oozie-site.xml 23946 11-05-17 00:28 /instrumentation.txt 37499 11-05-17 00:28 /java-sys-props.txt 3635 11-05-17 00:28 /os-env-vars.txt 279 11-05-17 00:28 /queue-dump.txt 38423 11-05-17 00:28 /sharelib.txt 100476 11-05-17 00:28 /thread-dump.html {code} - {{/0000000-171105002642017-oozie-asas-W/info.txt}} contains state transitions - {{/0000000-171105002642017-oozie-asas-W/resolved-actions/mr-node.xml}} contains the resolved workflow action "mr-node" (e.g. EL expressions evaluated) - {{/0000000-171105002642017-oozie-asas-W/resolved-actions/launcher_mr-node.log}} is the launcher for the action (here I had a simple workflow with 1 MR action) - {{/0000000-171105002642017-oozie-asas-W/workflow.xml}} is the user's workflow (without EL evaluation) - {{/0000000-171105002642017-oozie-asas-W/log.txt}} contain the server logs of for the {{0000000-171105002642017-oozie-asas-W}} workflow > 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: Attila Sasvari > Attachments: OOZIE-2296-002.patch, OOZIE-2296-003.patch, > OOZIE-2296-004.patch, OOZIE-2296-005.patch, OOZIE-2296-006.patch, > OOZIE-2296-009.patch, OOZIE-2296-010.patch, OOZIE-2296-011.patch, > OOZIE-2296-012.patch, OOZIE-2296-013.patch, OOZIE-2296-014.patch, > OOZIE-2296-015.patch, OOZIE-2296-016.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)