Oozie Jobs Raise "JA009: Cannot initialize Cluster. Please check your configuration for mapreduce.framework.name" on BDA V3.0 (Doc ID 1910911.1)

Last updated on JULY 24, 2017

Applies to:

Big Data Appliance Integrated Software - Version 3.0 and later
x86_64

Symptoms

Running oozie jobs in Hue, on a Client/Edge server, or on the command line of a BDA raises:

2014-07-13 21:50:54,712 WARN org.apache.oozie.command.wf.ActionStartXCommand:
SERVER[bdanode04.example.com] USER[<user>] GROUP[-] TOKEN[] APP[<app_name>]
JOB[0000005-140711162913661-oozie-oozi-W] ACTION[0000005-140711162913661-oozie-oozi-W@hive-node]
Error starting action [hive-node]. ErrorType [TRANSIENT], ErrorCode [JA009],
Message [JA009: bad conf file: top-level element not <configuration>]
org.apache.oozie.action.ActionExecutorException: JA009: bad conf file: top-level
element not <configuration>
at org.apache.oozie.action.ActionExecutor.convertExceptionHelper(ActionExecutor.java:412)
at org.apache.oozie.action.ActionExecutor.convertException(ActionExecutor.java:396)
at org.apache.oozie.action.hadoop.JavaActionExecutor.setupActionConf(JavaActionExecutor.java:397)
org.apache.oozie.action.ActionExecutorException: JA009: Cannot initialize Cluster.
Please check your configuration for mapreduce.framework.name and the correspond server addresses.
    at org.apache.oozie.action.ActionExecutor.convertExceptionHelper(ActionExecutor.java:412)
    at org.apache.oozie.action.ActionExecutor.convertException(ActionExecutor.java:392)
    at org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:909)
    at org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1065)
    at org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:217)
    at org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:62)
    at org.apache.oozie.command.XCommand.call(XCommand.java:280)
    at org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:323)
    at org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:252)
    at org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:174)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    ...

 

Debugging Tips for JA009 on BDA 3.0.1/CDH 5.0.*

Since the error states:  "Please check your configuration for mapreduce.framework.name and the correspond server addresses", some additional debugging tips are:

1. In Cloudera Manager (CM) verify the mapreduce.framework.name property in the mapred-site.xml for the Oozie service:

a) Navigate to the mapred-site.xml and check it.
home > oozie > Instances >  select 'Any Role Type': Oozie Server > Check the oozie_server (node 4) > Processes > expand Show > check  mapred-site.xml (yarn-conf/mapred-site.xml)

b) Verify that the mapreduce.framework.name property in mapred.xml supports YARN. Since mapred-site.xml applies to all MapReduce jobs an incorrect setting could cause the reported error.

The setting for BDA 3.0.1/CDH 5.0.1 is:

<property>
    <name>mapreduce.framework.name</name>
    <value>yarn</value>
</property>


2. On Node 4 of the cluster, the Oozie Server, as 'root' user, grep for "HADOOP_MAPRED_HOME" in /var/log/oozie/oozie-instrumentation.log.

# grep HADOOP_MAPRED_HOME /var/log/oozie/oozie-instrumentation.log*

The expected output for BDA V3.0.1/CDH 5.0.* with a YARN implementation is like:

b) Verify content of /etc/alternatives

You can use dcli to check all nodes of the cluster.


5. Turn on debugging in CM and rerun the failing test to capture better diagnostic output.

a) Set the Oozie Server Logging Threshold to DEBUG.  The default is: INFO

i. Navigate to: home > oozie > Configuration > View and Edit > Oozie Server Default Group  > Logs > Oozie Server Logging Threshold

ii. Set the value to: DEBUG


b) Enable Oozie Server Logging Threshold debugging.

i. Navigate to: home > oozie > Configuration > View and Edit > Oozie Server Default Group > Advanced > Java Configuration Options for Oozie Server

i. Set to value to: Dmapreduce.framework.name=yarn

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