Am 22.02.2015 um 23:14 schrieb Chris Dagdigian <[email protected]>: > > > Yes SGE can handle dependencies between jobs and even dependencies between > tasks in a job array. > > The job dependency syntax depends on job naming in the most common use case, > here is a simple example: > > qsub -N DataStagerTask ./my-SGE-job.sh > > qsub -hold_jid DataStagerTask ./my-analytic-job.sh
Small addition (besides using a job id as argument): it's also possible to use a wild card in the argument to -hold_jid, i.e. having jobs foobar_north, foobar_south, foobar_west and foobar_east running, one can wait for "foorbar*" and the jobs submitted before the waiting one will be taken into account (but not later submitted ones which start with "foobar"). -- Reuti > The "-hold_jid <name>" argument is what makes the 2nd job dependent on the > 1st job exiting before it will run > > -Chris > > > >> Peng Yu <mailto:[email protected]> >> February 22, 2015 at 3:26 PM >> Hi Ed, >> >> I am wondering if SGE allows users to specify dependencies between >> jobs. For example, I may need job1 be finished before job2 is started, >> even thought there might be enough resource to run job2 at a given >> time. >> >> Would you please let me if SGE do so? Thanks. >> > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
