Hi,
I have a coordinator job that triggers every hour and waits on data
in /app/YYYY/MM/DD/HH directory. This coordinator job triggers a java
action in a workflow, which is a pipeline of several map reduce jobs.
One of these workflow jobs(the java action) triggered by coordinator
failed even before it started and the data is still in the input
directory. I want to rerun this job.
Here is the workflow.xml
<workflow-app name="hourly-job-runner" xmlns="uri:oozie:workflow:0.1">
<start to="run-hourly-jobs" />
<action name="run-hourly-jobs">
<java>
<job-tracker>${jobTracker}</job-tracker>
<name-node>${nameNode}</name-node>
<main-class>com.control.HourlyJobRunner</main-class>
<arg>${jobsToRun}</arg>
<arg>${wfInput}</arg>
<arg>${wfDailyWebOutput}</arg>
<arg>${wfDailyEmailOutput}</arg>
</java>
<ok to="end"/>
<error to="fail"/>
</action>
<kill name='fail'>
<message>Map/Reduce failed, error
message[${wf:errorMessage(wf:lastErrorNode())}]</message>
</kill>
<end name='end' />
</workflow-app>
This workflow.xml gets its parameters from the coordinator.xml. When I
try to rerun this workflow job (that was actually triggered by the
coordinator), I get an internal server error.
Should it be an issue to rerun the workflow job like this. I am thinking
it is probably not able to get the value for this parameters when I
rerun it. Is that right?
Is there a way to trigger this through oozie?
My alternative at this point is to run this job manually without oozie's
intervention.
Thanks,
Deepika