[
https://issues.apache.org/jira/browse/OOZIE-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240161#comment-16240161
]
Attila Sasvari commented on OOZIE-2296:
---------------------------------------
Executed tests locally:
{code}
Failed tests:
testImportInvalidDataLeavesTablesEmpty(org.apache.oozie.tools.TestDBLoadDump):
import should have been ended prematurely
Failed tests:
testMaterizationLookup(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand):
expected:<Mon Nov 06 09:20:11 CET 2017> but was:<Sun Nov 05 11:20:11 CET 2017>
Failed tests:
testJMXInstrumentation(org.apache.oozie.util.TestMetricsInstrumentation): Could
not fetch metric
{code}
I will investigate failure of {{testJMXInstrumentation}} and
{{testImportInvalidDataLeavesTablesEmpty}} soon (these should not be related to
the patch in my opinion). {{testMaterizationLookup}} is known to be flaky.
> 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, OOZIE-2296-017.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)
