[ 
https://issues.apache.org/jira/browse/OOZIE-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Kanter updated OOZIE-2296:
---------------------------------
    Attachment: OOZIE-2296.001.patch

001 patch attached.  

Here's the usage:
{noformat}
usage: OozieDiagBundleCollector [-jobs <id ...>] [-maxchildactions <n>]
       [-numbundles <n>] [-numcoordinators <n>] [-numworkflows <n>]
       [-oozie <url>] -output <dir>
A tool that collects a diagnostic bundle of information from Oozie
 -jobs <id ...>         Detailed information on the given job IDs will be
                        collected (default: none)
 -maxchildactions <n>   Maximum number of Workflow or Coordinator actions
                        that will be collected (default: 10)
 -numbundles <n>        Detailed information on the last n Bundles will be
                        collected (default: 0)
 -numcoordinators <n>   Detailed information on the last n Coordinators
                        will be collected (default: 0)
 -numworkflows <n>      Detailed information on the last n workflows will
                        be collected (default: 0)
 -oozie <url>           Required: Oozie URL (or specify with OOZIE_URL env
                        var)
 -output <dir>          Required: Directory to output the zip file
{noformat}

> 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, oozie-diag-bundle-1427851199786.zip
>
>
> 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.3.4#6332)

Reply via email to