Oozie workflow not working from web console

Lab Support
#1

Hi,

I am running the following command from web console and each time it is throwing connection timeout error.

oozie job -oozie http://ip-172-31-13-154.ec2.internal:11000/oozie -
config examples/apps/map-reduce/job.properties -run
Connection exception has occurred [ java.net.ConnectException Connection timed out (Connection timed out) ]. Try
ing after 1 sec. Retry count = 1
Connection exception has occurred [ java.net.ConnectException Connection timed out (Connection timed out) ]. Try
ing after 2 sec. Retry count = 2

Also I the job.properties is updated with the following values:
nameNode=hdfs://ip-172-31-53-48.ec2.internal:8020
jobTracker=ip-172-31-53-48.ec2.internal:8050

Please advise if something is wrong. Thanks.

1 Like
#2

@Rajasekhar_Rao,

Oozie hostname has been changed to “http://ip-172-31-20-247.ec2.internal:11000/oozie”,
even though if we used updated hostname, it is not responding & got same exception. Raised to CloudXLab. Need some support from them.

@abhinav, @abhinavsingh, @sgiri, Can you please look into this??

#3

@raviteja,

Thank you for bringing it to notice. Hope it is working fine now.

#4

@abhinav, @abhinavsingh, @sgiri,
this issue is still there, not solved, please address it. it’s been more than 20 days.

#5

@abhinavsingh, @sgiri

Hi,

What is the update on this? Its been more than 2 weeks and it is still not working. Can you please resolve this issue as it is impeding the users very badly. This is really getting frustrating as the admins are not even responding to this issue in a timely fashion. Would appreciate your kind response.

This is the error i am getting today:

[srajasekharrao@ip-172-31-38-146 oozie]$ oozie job -oozie http://ip-172-31-20-247.ec2.internal:11000/oozie -config examples/apps/map-reduce/job.properties -run
Error: E0501 : E0501: Could not perform authorization operation, Call From ip-172-31-20-247.ec2.internal/172.31.20.247 to ip-172-31-53-48.ec2.internal:8020 failed on so
cket timeout exception: org.apache.hadoop.net.ConnectTimeoutException: 20000 millis timeout while waiting for channel to be ready for connect. ch : java.nio.channels.So
cketChannel[connection-pending remote=ip-172-31-53-48.ec2.internal/172.31.53.48:8020]; For more details see: http://wiki.apache.org/hadoop/SocketTimeout
[srajasekharrao8669@ip-172-31-38-146 oozie]$

Thanks,
Raj

#6

I tested spark on oozie using Hue. It was working fine.

#7

Can you advise why it is not working when you try to run the Oozie job through web console ?

I need to run the oozie jobs via web console.

1 Like
#8

@Rajasekhar_Rao

Can you paste your job.properties?

I can see that you are using the wrong HDFS and job tracker URLs

#9

Hi @abhinav,

below are job.properties:

nameNode=hdfs://ip-172-31-53-48.ec2.internal:8020
jobTracker=ip-172-31-53-48.ec2.internal:8050
queueName=default
examplesRoot=oozie_works/cxl_examples/examples
oozie.wf.application.path=${nameNode}/user/${user.name}/${examplesRoot}/apps/map-reduce/workflow.xml
outputDir=map-reduce

#10

@raviteja,

The URLs are wrong. Please find the updated URLs in Ambari.

1 Like
#11

Hi @abhinav,

yes, nameNode & jobTracker url’s are wrong: Correct properties are below:

nameNode=hdfs://ip-172-31-35-141.ec2.internal:8020
jobTracker=ip-172-31-35-141.ec2.internal:8050
queueName=default
examplesRoot=examples
oozie.wf.application.path=${nameNode}/user/${user.name}/${examplesRoot}/apps/map-reduce/workflow.xml
outputDir=map-reduce

1 Like