Hi Maxime, Thank you very much for your answer. It is all what I needed to know.
Regards, Étienne On 21 June 2012 17:43, Maxime Petazzoni <[email protected]> wrote: > * Etienne Dumoulin <[email protected]> [2012-06-21 11:10:36]: > > > From what Mona pointed out: "the action is materializes when input > > dependencies are satisfied". If I start a coordinator with a starting > > date one year earlier that the current date, and I have a daily job with > > a timeout of -1. Does Oozie creates 365 jobs as soon as the input-event > > is satisfied ? If the input-event and output-event are satisfied, does > > oozie try to run the job anyway? If yes, is there a solution to generate > > the opposite behaviour in the workflow? > > I don't think it will start workflows for the backlog. It will just > start materializing on a go-forward basis the next time the defined > frequency hits. > > > A more independent questions. Is it possible to change the coordinator > > on the fly? Let say I have a job running at midnight, I want to make it > > start at 1 am instead without affecting what is running and the stack of > > job to run. Is that possible or I have to wait that everything is > > finished for the date YYYYMMDD, and reload a workflow starting at the > > date YYYYMM{DD+1}. > > You can change a few parameters of a coordinator while it is loaded: the > end date, the concurrency and set a pause time. See > > http://incubator.apache.org/oozie/docs/3.2.0-incubating/docs/DG_CommandLineTool.html#Changing_endtimeconcurrencypausetime_of_a_Coordinator_Job > > In your case you would have to change the end date of the running > coordinator to make it stop gracefully and start a new one with the new > frequency I think. > > /Max > -- > { name: 'Maxime Petazzoni', title: 'Sr. Platform Engineer', > company: { name: 'Turn, Inc', url: 'http://www.turn.com' } } >
