That is indirectly enabled by concurrency control, but which is at Coordinator action level right now and not Coordinator job that Bundle kicks off. What can be done is, using different Start and End times for your different coordinators in order to stagger them. Please see the example referred here for parametrizing start times.
http://oozie.apache.org/docs/3.2.0-incubating/BundleFunctionalSpec.html#a3. _Expression_Language_for_Parameterization -- Mona Chitnis On 11/19/12 10:42 AM, "Yongcheng Li" <[email protected]> wrote: >Is it possible to have two coordinator apps run one after another, i.e. >the second one starts after the first one ends? I don't want to kick off >all the coordinator apps simultaneously to fight for limited system >resource. > >Thanks! > >Yongcheng > >-----Original Message----- >From: Mona Chitnis [mailto:[email protected]] >Sent: Monday, November 19, 2012 1:37 PM >To: [email protected] >Subject: Re: Multiple Actions for Coordinator App > >Hi, > >You are right that for two separate workflows, you will need two >coordinator apps corresponding to each. In order to combine common >properties and also to have a single place of control, try using a >'Bundle' which is a combination of coordinators. >-- >Mona Chitnis > > > > >On 11/19/12 10:08 AM, "Yongcheng Li" <[email protected]> wrote: > >>Hi, >> >>I have several independent workflow apps I need to run. They share many >>properties and I feel that it makes sense to put them in just one >>coordinator application. However, a coordinator application only allows >>one action which only allows one workflow app in it. So I need to >>either combine the two independent workflow applications into one or >>create two separate coordinator apps. Does it make sense to allow >>multiple actions or workflow apps in one coordinator app? If not, what >>is the best practice for this scenario? >> >>Thanks! >> >>Yongcheng > > >
