Hi, Am 27.02.2014 um 13:35 schrieb Riccardo Murri:
> I would like to reserve a few nodes on the cluster for interactive > usage. I've created an `interactive.q` for that, and set its `qtype` > to `INTERACTIVE`. > > I would also like users to be able to start parallel jobs > interactively (for debugging purposes), so the `interactive.q` is > linked to all the parallel environments:: > > # qconf -sq interactive.q | egrep 'qtype|pe_list' > qtype INTERACTIVE > pe_list intel-mpi2_mpd mpich1_rsh mpich2_rsh openmpi > openmpi2 \ > > However, I have seen cases where a batch parallel job is started on a > mixture of queue instances, which *include* slots from the > `interactive.q`. > > Is this a bug or is it rather likely that I have mistakes in the config? Well - it's just the way it's implemented. Any attached PE to a queue allows also parallel batch jobs to start. You may call it a feature or a bug. What about a JSV to attach a list of queues of only eligible queues to all PE jobs? NB: "INTERACTIVE" is more like "IMMEDIATE". You can start any batch job in an interactive queue by: $ qsub -now yes ... resp. $ qrsh -now no will go to a "BATCH" queue. -- Reuti > Thanks for any suggestions! > > Kind regards, > Riccardo > > -- > Riccardo Murri > http://www.gc3.uzh.ch/people/rm > > Grid Computing Competence Centre > University of Zurich > Winterthurerstrasse 190, CH-8057 Zürich (Switzerland) > Tel: +41 44 635 4222 > Fax: +41 44 635 6888 > > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users > _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
