My Oracle Support Banner

The Oozie Cluster Verificaiton Test Fails with "./mammoth -c" or Stand-alone with "uber-SubtaskRunner" Found in the Logs Indicating Uber Mode is Enabled (Doc ID 2272971.1)

Last updated on MARCH 28, 2023

Applies to:

Big Data Appliance Integrated Software - Version 4.6.0 and later
Linux x86-64

Symptoms

NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.

The Oozie cluster verification test fails with "./mammoth -c" or when run stand-alone when Uber mode is enabled on the cluster.  This may show up after upgrade. 

The Oozie cluster verification failure looks like below.  The Oozie cluster verification test is part of the BDA distribution.

Running oozie test workflow which includes a map-reduce step, a sqoop step, a hive step, a streaming step and a pig step
existing file removed
local temp dir created
staring oozie workflow

oozie job ID is: 0000000-<ID>-oozie-oozi-W
oozie job runing...
oozie job runing...
oozie job runing...
...<many oozie job running ...>
oozie job runing...
oozie job runing...
oozie job runing...
Job ID : 0000000-<ID>-oozie-oozi-W
------------------------------------------------------------------------------------------------------------------------------------
Workflow Name : combine-wf
App Path : hdfs://<CLUSTER_NAME>-ns/user/oracle/oozie-example/apps/combine
Status : KILLED
Run : 0
User : oracle
Group : -
Created : 2017-05-31 07:44 GMT
Started : 2017-05-31 07:44 GMT
Last Modified : 2017-05-31 07:47 GMT
Ended : 2017-05-31 07:47 GMT
CoordAction ID: -

Actions
------------------------------------------------------------------------------------------------------------------------------------
ID Status Ext ID Ext Status Err Code
------------------------------------------------------------------------------------------------------------------------------------
0000000-<ID>-oozie-oozi-W@:start: OK - OK -
------------------------------------------------------------------------------------------------------------------------------------
0000000-<ID>-oozie-oozi-W@cleanup-node OK - OK -
------------------------------------------------------------------------------------------------------------------------------------
0000000-<ID>-oozie-oozi-W@pig-node OK job_<JOBID>_0001 SUCCEEDED -
------------------------------------------------------------------------------------------------------------------------------------
0000000-<ID>-oozie-oozi-W@hive-node OK job_<JOBID>_0005 SUCCEEDED -
------------------------------------------------------------------------------------------------------------------------------------
0000000-<ID>-oozie-oozi-W@sqoop-node OK job_<JOBID>_0008 SUCCEEDED -
------------------------------------------------------------------------------------------------------------------------------------
0000000-<ID>-oozie-oozi-W@streaming-node ERROR job_<JOBID>_0010 FAILED/KILLED-
------------------------------------------------------------------------------------------------------------------------------------
0000000-<ID>-oozie-oozi-W@fail OK - OK E0729
------------------------------------------------------------------------------------------------------------------------------------

Oozie failed

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.