This job succeeded and I got the output before. Now its in PREP state
*job.properties,*
{{{
user.name=ram
nameNode=hdfs://IP:8020
jobTracker=IP:8050
queueName=default
oozie.use.system.libpath=true
oozie.wf.application.path=${nameNode}/user/${user.name}/count
}}}
*workflow.xml*
{{{
<?xml version="1.0" encoding="UTF-8"?>
<workflow-app xmlns="uri:oozie:workflow:0.4" name="workflow">
<start to="Spark0" />
<action name="Spark0">
<shell xmlns="uri:oozie:shell-action:0.2">
<job-tracker>${jobTracker}</job-tracker>
<name-node>${nameNode}</name-node>
<configuration>
<property>
<name>mapred.job.queue.name</name>
<value>${queueName}</value>
</property>
</configuration>
<exec>count.sh</exec>
</shell>
<ok to="end" />
<error to="fail" />
</action>
<kill name="fail">
<message>job failed, error
message[${wf:errorMessage(wf:lastErrorNode())}]</message>
</kill>
<end name="end" />
</workflow-app>
}}}
On Fri, Apr 15, 2016 at 12:24 PM, Morgrim Murdargent <
[email protected]> wrote:
> Hello !
>
> To help you, we neef the workflow.xml and the properties.
>
> BR.
>
> Morgrim
> Le 15 avr. 2016 08:26, "ram kumar" <[email protected]> a écrit :
>
> > Hi,
> >
> > I ran a oozie workflow job manually, it worked fine.
> > When re submitting the same job via Hue, it stuck in PREP (preparing)
> > state.
> > I tried to kill the job,
> >
> > following log appears in oozie.log
> > {{{
> > 2016-04-15 02:19:45,048 INFO DagEngine:520 -
> > SERVER[761029-*test-qahadoop1.vocollectvoice.com
> > <http://test-qahadoop1.vocollectvoice.com>] USER[ram] GROUP[-] TOKEN[-]
> > APP[-] JOB[0000008-160406191931812-oozie-oozi-W] ACTION[] User ram killed
> > the WF job 0000008-160406192-oozie-oozi-W*
> > 2016-04-15 02:19:46,703 INFO
> > CoordMaterializeTriggerService$CoordMaterializeTriggerRunnable:520 -
> > SERVER[
> > 761029-test-qahadoop1.vocollectvoice.com] USER[-] GROUP[-] TOKEN[-]
> APP[-]
> > JOB[-] ACTION[-] CoordMaterializeTriggerService - Curr Date=
> > 2016-04-15T06:24Z, Num jobs to materialize = 0
> > 2016-04-15 02:19:46,703 INFO
> > CoordMaterializeTriggerService$CoordMaterializeTriggerRunnable:520 -
> > SERVER[
> > 761029-test-qahadoop1.vocollectvoice.com] USER[-] GROUP[-] TOKEN[-]
> APP[-]
> > JOB[-] ACTION[-] Released lock for
> > [org.apache.oozie.service.CoordMaterializeTriggerService]
> > 2016-04-15 02:20:00,971 INFO
> > StatusTransitService$StatusTransitRunnable:520 - SERVER[
> > 761029-test-qahadoop1.vocollectvoice.com] USER[-] GROUP[-] TOKEN[-]
> APP[-]
> > JOB[-] ACTION[-] Acquired lock for
> > [org.apache.oozie.service.StatusTransitService]
> > 2016-04-15 02:20:00,971 INFO
> > StatusTransitService$StatusTransitRunnable:520 - SERVER[
> > 761029-test-qahadoop1.vocollectvoice.com] USER[-] GROUP[-] TOKEN[-]
> APP[-]
> > JOB[-] ACTION[-] Running coordinator status service from last instance
> time
> > = 2016-04-15T06:19Z
> > 2016-04-15 02:20:00,971 INFO PauseTransitService:520 - SERVER[
> > 761029-test-qahadoop1.vocollectvoice.com] USER[-] GROUP[-] TOKEN[-]
> APP[-]
> > JOB[-] ACTION[-] Acquired lock for
> > [org.apache.oozie.service.PauseTransitService]
> > 2016-04-15 02:20:00,972 INFO
> > StatusTransitService$StatusTransitRunnable:520 - SERVER[
> > 761029-test-qahadoop1.vocollectvoice.com] USER[-] GROUP[-] TOKEN[-]
> APP[-]
> > JOB[-] ACTION[-] Running bundle status service from last instance time =
> > 2016-04-15T06:19Z
> > 2016-04-15 02:20:00,972 INFO
> > StatusTransitService$StatusTransitRunnable:520 - SERVER[
> > 761029-test-qahadoop1.vocollectvoice.com] USER[-] GROUP[-] TOKEN[-]
> APP[-]
> > JOB[-] ACTION[-] Released lock for
> > [org.apache.oozie.service.StatusTransitService]
> > 2016-04-15 02:20:00,972 INFO PauseTransitService:520 - SERVER[
> > 761029-test-qahadoop1.vocollectvoice.com] USER[-] GROUP[-] TOKEN[-]
> APP[-]
> > JOB[-] ACTION[-] Released lock for
> > [org.apache.oozie.service.PauseTransitService]
> > }}}
> >
> > But in UI, the job still in *PREP* state
> >
> > When submitting new job via CLI, its going to PREP state
> > Can any1 help me with this?
> >
> > Thanks.
> >
>
