You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@oozie.apache.org by Scott Preddy <sc...@gmail.com> on 2014/03/03 18:06:42 UTC
why is workflow not being executed by coordinator?
data set in question exists at <name node>/Table/20140228
Workflow was not kicked off. What am I missing? Thanks.
<coordinator-app name="service-coord" frequency="${coord:days(1)}"
start="${startTime}" end="${endTime}"
timezone="UTC"
xmlns="uri:oozie:coordinator:0.1">
<datasets>
<dataset name="Table" frequency="${coord:days(1)}"
initial-instance="${startTime}" timezone="UTC">
<uri-template>hdfs://<my
path>/Table/${YEAR}${MONTH}${DAY}</uri-template>
</dataset>
</datasets>
<input-events>
<data-in name="input" dataset="Table">
<instance>${startTime}</instance>
</data-in>
</input-events>
<action>
<workflow>
<app-path>hdfs://<my path>/oozie/build/service</app-path>
<configuration>
<property>
<name>param1</name>
<value>${param1}</value>
</property>
<property>
<name>param2</name>
<value>${param2}</value>
</property>
</configuration>
</workflow>
</action>
</coordinator-app>
----------------------------------------------------------
where job.properties:
nameNode=<hdfs url>
jobTracker=<hdfs address>
queueName=<my user name>
buildRoot=oozie/build
oozie.coord.application.path=${nameNode}/user/${user.name
}/${buildRoot}/coordinator
populationId=demo
documentTableId=20140228
startTime=2014-02-28T22:35Z
endTime=2014-02-28T22:35Z
----------------------------------------------------------
log:
2014-02-28 16:33:33,246 INFO CoordSubmitXCommand:539 - USER[<my user
name>] GROUP[-] TOKEN[] APP[service-coord]
JOB[0000136-140120213435108-oozie-oozi-C] ACTION[-]
ENDED Coordinator Submit jobId=0000136-140120213435108-oozie-oozi-C
2014-02-28 16:33:33,353 INFO CoordMaterializeTransitionXCommand:539 -
USER[<my user name>] GROUP[-] TOKEN[] APP[service-coord]
JOB[0000136-140120213435108-oozie-
oozi-C] ACTION[-] materialize actions for tz=Coordinated Universal Time,
start=Fri Feb 28 16:35:00 CST 2014, end=Fri Feb 28 16:35:00 CST 2014,
timeUnit 5,
frequency :1:DAY,
lastActionNumber 0
2014-02-28 16:33:33,358 INFO CoordMaterializeTransitionXCommand:539 -
USER[<my user name>] GROUP[-] TOKEN[] APP[service-coord]
JOB[0000136-140120213435108-oozie-
oozi-C] ACTION[-] [0000136-140120213435108-oozie-oozi-C]: Update status
from PREP to RUNNING
2014-02-28 16:33:33,358 INFO CoordMaterializeTransitionXCommand:539 -
USER[<my user name>] GROUP[-] TOKEN[] APP[service-coord]
JOB[0000136-140120213435108-oozie-
oozi-C] ACTION[-] [0000136-140120213435108-oozie-oozi-C]: all actions have
been materialized, job status = RUNNING, set pending to true
Back
java-launcher.jar not found
Posted by Yann Luppo <Ya...@LiveNation.com>.
Hi,
I have a workflow that runs just fine when I submit manually as a simple
workflow but when I try schedule it via a coordinator setup it throws this
error:
Error initializing attempt_201402111351_1710_m_000000_2
java.io.FileNotFoundException: Requested file
/user/myuser/oozie-mapr/0000201-140225173647925-oozie-mapr-W/MyMRJob--java/
java-launcher.jar does not exist. at
com.mapr.fs.MapRFileSystem.getMapRFileStatus(MapRFileSystem.java:805) at
com.mapr.fs.MapRFileSystem.getFileStatus(MapRFileSystem.java:815) at
org.apache.hadoop.filecache.TaskDistributedCacheManager.setupCache(TaskDist
ributedCacheManager.java:186) at
org.apache.hadoop.mapred.TaskTracker$4.run(TaskTracker.java:1548) at
java.security.AccessController.doPrivileged(Native Method) at
javax.security.auth.Subject.doAs(Subject.java:396) at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.j
ava:1127) at
org.apache.hadoop.mapred.TaskTracker.initializeJob(TaskTracker.java:1540)
at org.apache.hadoop.mapred.TaskTracker.localizeJob(TaskTracker.java:1425)
at org.apache.hadoop.mapred.TaskTracker$6.run(TaskTracker.java:3802)
I checked on HDFS at the location specified and indeed there is no *.jar
file there.
Where does that java-launcher come from? How do I get it placed in the
cache so it can get picked up?
Thanks