Hi Thomas, Can you try waiting about 10 minutes and see if it switches to SUCCEEDED? If that's happening, then it means the callbacks from the AM are not getting through to Oozie. The AM logs might have more information on what's going wrong.
- Robert On Wed, Sep 3, 2014 at 2:20 AM, Thomas Larsson <[email protected]> wrote: > I forgot to mention, I am running CDH 5.0.3, i.e. Oozie 4.0.0. > > > On Wed, Sep 3, 2014 at 11:08 AM, Thomas Larsson <[email protected] > > > wrote: > > > Hello. > > > > I have a problem similar to what has been asked before but with enough of > > a difference to make previous solutions not applicable for me. > > > > I am running a simple workflow with a sqoop action and the launcher task > > hangs in state RUNNING. > > In previous questions I have seen that their action tasks are not getting > > started, but this is not the case for me. My action task has succeeded. > > > > No logs show any indication of what is happening. > > > > Do you have any suggestions on how to investigate this? > > > > Here is my workflow definition: > > > > <?xml version="1.0" encoding="UTF-8"?> > > <workflow-app xmlns="uri:oozie:workflow:0.4" name="${jobName}"> > > > > <start to="runSqoop"/> > > > > <action name="runSqoop"> > > <sqoop xmlns="uri:oozie:sqoop-action:0.2"> > > <job-tracker>${jobTracker}</job-tracker> > > <name-node>${nameNode}</name-node> > > <command>censored</command> > > </sqoop> > > <ok to="end"/> > > <error to="kill"/> > > </action> > > <kill name="kill"> > > <message>Oozie job "${jobName}" > > ${hueUrl}/oozie/list_oozie_workflow/${wf:id()}// (jobtracker > > [${jobTracker}], namenode [${nameNode}]) failed at (wf:lastErrorNode()) > > with error message ${wf:errorMessage(wf:lastErrorNode())}</message> > > </kill> > > > > <end name="end"/> > > </workflow-app> > > > > Best Regards > > /Thomas > > >
