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 JUNE 04, 2017

Applies to:

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

Symptoms

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:

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-170531090119988-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-170531090119988-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-170531090119988-oozie-oozi-W@:start: OK - OK -
------------------------------------------------------------------------------------------------------------------------------------
0000000-170531090119988-oozie-oozi-W@cleanup-node OK - OK -
------------------------------------------------------------------------------------------------------------------------------------
0000000-170531090119988-oozie-oozi-W@pig-node OK job_1496214048673_0001 SUCCEEDED -
------------------------------------------------------------------------------------------------------------------------------------
0000000-170531090119988-oozie-oozi-W@hive-node OK job_1496214048673_0005 SUCCEEDED -
------------------------------------------------------------------------------------------------------------------------------------
0000000-170531090119988-oozie-oozi-W@sqoop-node OK job_1496214048673_0008 SUCCEEDED -
------------------------------------------------------------------------------------------------------------------------------------
0000000-170531090119988-oozie-oozi-W@streaming-node ERROR job_1496214048673_0010 FAILED/KILLED-
------------------------------------------------------------------------------------------------------------------------------------
0000000-170531090119988-oozie-oozi-W@fail OK - OK E0729
------------------------------------------------------------------------------------------------------------------------------------

Oozie failed

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms