[torqueusers] Dependencies among several jobs
dgolden at cp.dias.ie
Mon Aug 28 09:47:39 MDT 2006
On Friday 25 August 2006 23:44, Vincenzo Di Nicola wrote:
> create a script file: there I submit each single job, read
> its jobid, and use the "-W depend=afterany" option with regard to the
> previous job ids.
Well, that is what we tend to do, e.g. a simple string of 10 jobs:
HEADJOB=$(qsub -h myjob.pbs)
for i in $(seq 1 9); do
DEPJOB=$(qsub -W "depend=afterok:$DEPJOB" myjob.pbs)
qrls -h u $HEADJOB
> But is there a nicer way to enforce dependencies, maybe without having to
> rely on a jobid (but perhaps a job name)?
Well, as far as I know, no. Condor DAGman IIRC allows a more declarative
dependency graph specification method, but this is the Torque list :-)
(Aside: Lately (2.1.0p0) I think I'm seeing some weirdness where sometimes,
when the head job disappears (perhaps abnormally due to some system fault)
the dependent jobs don't notice, kinda like the dependency doesn't "fire"
("edge-" instead of "level-" triggered maybe?), and then left with a bunch of
held jobs in the queue. Haven't pinned it down yet, and due an upgrade again
shortly anyway, may well just be an already-fixed bug or even intended
behaviour. Can't replicate on-demand, unfortunately)
More information about the torqueusers