Reply
New Contributor
Posts: 1
Registered: ‎04-28-2015

Right oozie job.properties for CDH 5.3.0 (PREP status for a very long time)

Hi,

 

I'm using cloudera-quickstart-vm-5.3.0 and I'm having problems running java actions in oozie: They remain in PREP status for a very long time, and finally fail with the following error message:

 

"Call From quickstart.cloudera/127.0.0.1 to localhost:8021 failed on connection exception: java.net.ConnectException: Connection refused; For more details see:  http://wiki.apache.org/hadoop/ConnectionRefused"

 

I use the below job.properties file:

 

nameNode=hdfs://localhost:8020
jobTracker=localhost:8021

queueName=default

oozie.wf.application.path=hdfs://localhost:8020/user/cloudera/app/oozie
oozie.wf.use.system.libpath=true
oozie.libpath=hdfs://localhost:8020/user/cloudera/share/lib

 

As far as I know, CDH 5.3 uses a YARN architecture, and no longer jobTracker is used. But then...

 

Which should be the right job.properties configuration ? or.. which should be the right property for 'jobTracker' ? 

 

Thank you very much in advance

Highlighted
Cloudera Employee
Posts: 35
Registered: ‎07-08-2013

Re: Right oozie job.properties for CDH 5.3.0 (PREP status for a very long time)

Oozie can work with both MR1 and MR2 (YARN), though not at the same time.  The VM is configured for MR2 out of the box, but the examples that ship with Oozie target MR1.  You can point the example at MR2 by simply changing the "jobTracker" parameter from jobTracker=localhost:8021 (the JT) to jobTracker=localhost:8032 (the RM).  Even though it's called "jobTracker", Oozie will use MR2 if you point it at an RM.

Software Engineer | Cloudera, Inc. | http://cloudera.com
Announcements

Our community is getting a little larger. And a lot better.


Learn More about the Cloudera and Hortonworks community merger planned for late July and early August.