I have been running crunch/cascading jobs as oozie java actions, no
problems so far.
On Tue, Oct 8, 2013 at 4:47 PM, Alejandro Abdelnur wrote:
> I would suggest looking at how Pig/Hive/Sqoop/Distcp actions works if you
> want to have a custom action. Which, BTW, it would be a great
> contributi
Hi Mohammad,Thanks for your reply. I know all of those options. I am looking
for something which can run automatically or a way of changing coordinator's
default behavior.
Thanks,
Tanzir
> Date: Wed, 16 Oct 2013 11:59:40 -0700
> From: misla...@yahoo.com
> Subject: Re: Force a coordinator job t
Hi Tanzir,
There are multiple ways to stop coordinator.
1. Reset the end time or pause time
http://oozie.apache.org/docs/3.3.2/DG_CommandLineTool.html#Changing_endtimeconcurrencypausetime_of_a_Coordinator_Job
2. Kill the job "oozie job -kill "
3. Suspend a job "oozie job -suspend "
Regards,
Mo
Hello all,I've been using Oozie coordinator job for a while now. I'm just
wondering is there any way to force a coordinator job to stop? Generally if one
of the workflows is failed, Oozie continues to try following workflows and at
the end it turns the coordinator job into DONEWITHERROR status.
