Hi,

I am trying to run an Oozie workflow that comprises of an action node to
invoke Pig script.Its using the YARN framework.

Hadoop version: 2.7.1
Oozie version: 4.2.0

The problem is that when I am trying to run the workflow using any normal
user (other than yarn),I am getting below error message in the job history
logs:
*bdeb* is the user I am using to submit the workflow.
==============================
Job init failed : *org.apache.hadoop.yarn.exceptions.YarnRuntimeException:
java.io.FileNotFoundException: File does not exist:
hdfs://localhost:8020/user/bdeb/.staging/job_1464598574860_0051/job.splitmetainfo*
at
org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl$InitTransition.createSplits(JobImpl.java:1568)
at
org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl$InitTransition.transition(JobImpl.java:1432)
at ...............
at
org.apache.hadoop.mapreduce.v2.app.MRAppMaster$JobEventDispatcher.handle(MRAppMaster.java:1312)
at
org.apache.hadoop.mapreduce.v2.app.MRAppMaster.serviceStart(MRAppMaster.java:1080)

=================================

Permission of /user/bdeb:
drwxrwxr-x  3 bdeb     hadoop    4096 May 26 17:36 bdeb

Permission of /user/bdeb/.staging :
drwx------    10 bdeb    hadoop    4096 Jun  2 00:07 .staging

It seems even though I am trying to submit the workflow as bdeb
user,internally yarn user is trying to read/write files under bdeb/.staging
and failing because of no read perms available.

*The error disappears if I submit the Oozie workflow using
-Duser.name=yarn.*

I read somewhere that there was a defect in Oozie related to error while
trying to submit workflow using a non-yarn user which was fixed way
back.But as you can see above,The Hadoop and Oozie versions I am using are
quite recent compared to the time of that defect fix.Could it be possible
that the defect has crept in again?

Please help.

Thanks

Reply via email to