Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Jobtracker HA and oozie

avatar
Rising Star

Hello, I have a hadoop cluster with CDH 4.4.0 and HDFS HA and JobTracker HA.

I tried to lunch oozie workflow but got this:

 

JA006: Call From xxxx to xxxx failed on connection exception: java.net.ConnectException: Connection refused; For more details see:http://wiki.apache.org/hadoop/ConnectionRefused

 

I found this: https://issues.cloudera.org/browse/HUE-1631

 

But I don't know how to fix my problem. Where to configure oozie to work with JobTracker HA?

 

1 ACCEPTED SOLUTION

avatar
Super Collaborator

Hey Markovich,

 

Are you running the workflow from inside Hue or from the Oozie command line?  If from within Hue, then you are running into HUE-1631 and it won't be fixed until a later release of CDH.  If you are not using Hue, can you attach your job.properties file and workflow?

 

Thanks
Chris

View solution in original post

11 REPLIES 11

avatar
New Contributor

Hi cconnor,

 

thanks for the reply! We're running CDH 4.6 with CM 4.8.2 and to me it looks like that at least CM doesn't configure the logical_name property automatically yet, does it? Also I can't find a dedicated config field in CM. So I suppose the safety valve is still they way to go?

 

Thanks in advance!

avatar
Super Collaborator

That's right, you'll have to put the following in your Hue Service->Configuration->Hue Server->Advanced->Hue Server Configuration Safety Valve for hue_safety_valve_server.ini:

 

 

[hadoop]
[[mapred_clusters]]
[[[default]]]
jobtracker_host=cdh45-2.qa.test.com
thrift_port=9290
jobtracker_port=8021
submit_to=true
hadoop_mapred_home={{HADOOP_MR1_HOME}}
hadoop_bin={{HADOOP_BIN}}
hadoop_conf_dir={{HADOOP_CONF_DIR}}
security_enabled=true
logical_name=logicaljt
[[[jtha]]]
jobtracker_host=cdh45-1.qa.test.com
thrift_port=9290
jobtracker_port=8021
submit_to=true
hadoop_mapred_home={{HADOOP_MR1_HOME}}
hadoop_bin={{HADOOP_BIN}}
hadoop_conf_dir={{HADOOP_CONF_DIR}}
security_enabled=true
logical_name=logicaljt

 

 

Leaving off "secuirty_enabled=true" if you're not using kerberos.