Hi, Am 18.02.2011 um 16:25 schrieb Chris Jewell:
> This feels like I ought to know better, but..... I currently have two > queues: "batch.q" which is configured to accept both batch and interactive > jobs, and "interactive.q" which just accepts interactive jobs. Both are > configured to use a PE 'smp' which is configured as $pe_slots. The queues > are configured such that batch.q is Sequence Nr 0, and interactive.q is > Sequence Nr 1. This means that when the cluster is busy, nodes will be > oversubscribed by (niced) interactive jobs (characterised by short, sharp > bursts of activity, with long idle periods) only, thus preserving some sense > of "availability". > > Our cluster was busy the other day, and to my surprise I found that when I > submitted a parallel job using "qsub -pe smp 4 myScript.com", it ended up > scheduled in interactive.q. Huh? interactive.q is not configured to accept > batch jobs. Anyone know what might be going on? The term "interactive" is more in a sense of "immediate". With "-now n", resp. "-now y", you can run an interactive job in a batch only queue or a batch job in an interactive only queue. For parallel jobs it's like an implied batch queue. The qtype in the queue definition will only be considered for interactive jobs in this case. But even if qtype is set to NONE (or BATCH), you can run a parallel interactive jobs by using "-now n" therein though. -- Reuti > Cheers, > > Chris > -- > Dr Chris Jewell > Department of Statistics > University of Warwick > Coventry > CV4 7AL > UK > Tel: +44 (0)24 7615 0778 > > > > > > > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
