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.
