<[email protected]> writes: > => is there a way to allow running on par.q@@group1 or par.q@@group2 but never > => on both ? > > You could: > > put both groups into the same queue > > assign a boolean attribute to each group (for example, > each server in "group1" has the attribute "group1") > > The submission would look like: > > qsub -q combined_groups -l group1 myjob > > or > > qsub -q combined_groups -l group2 myjob > > > Without specifying the resource requirement, the job would be free to run in > either group, a benefit for things like single-slot jobs, as in:
That's exactly what you don't want. You really want separate PEs for islands of connectivity which you want to schedule according to which is available. Similarly if you have groups of significantly different hardware on the same fabric which would make for unbalanced MPI jobs. I know this only too well with four separate fabrics and five relevant types of cpu... -- Community Grid Engine: http://arc.liv.ac.uk/SGE/ _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
