One way you might be able to do this is have the coordinator have an input event path instance be timestamped to the minute and have the coordinator job run every minute as well. Then, the last thing the job will do before finishing is to create one of those timestamped paths with the current minute + a safety offset (maybe just a minute). As an example, job X finishes at 1:23 AM and creates a directory named 0124. Job Y was scheduled to run at 1:24 AM. When it starts, it sees the directory present, so it executes. Job Z was scheduled to run at 1:23 AM, but a directory named 0123 was never created, so it never executes.
-- Chris On Tue, Apr 23, 2013 at 5:22 AM, Tousif <[email protected]> wrote: > Hi, > > I would like to run a coordinator job in a loop. As soon as existing job > finishes it > should start same job again , Here job runs for unpredictable time. > > -- > > > Regards > Khazi >
