[ 
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-003.patch

So far I only added just a couple of unit tests for validating user input.

Unfortunately, in its current form, MiniOozieTestCase cannot be used for 
testing the tool. {{getClient()}} of {{LocalOozie}} can only be used to run 
workflows and get wf statuses. It does not provide full oozie API. Many REST 
API calls (such as listing environment variables, sys props, sharelibs, etc.) 
result in errors / no-op. If TestOozieDiagBundleCollector extended 
MiniOozieTestCase, other tool tests like TestOozieDBCLI would have impact on 
these tests too (resources contain {{fake-oozie-site.xml}} and 
{{hsqldb-oozie-site.xml}}).

> 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
>
>
> 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)

Reply via email to