[torqueusers] enforcing ppn=X limits on per queue level

Garrick Staples garrick at usc.edu
Thu Aug 30 11:52:04 MDT 2007


On Thu, Aug 30, 2007 at 07:13:41PM +0200, Thomas Zeiser alleged:
> Dear All,
> 
> in our cluster, we have a mixture of nodes with 2 and 4 CPUs which
> are served by different queues (but the same tqoeue server). Is
> there a way that e.g. the "max2cpus-per-node" queue directly
> rejects any jobs which specify "ppn=4" as they cannot be started
> there at all? Right now they are accepted but get deferred (and
> users sometimes do not realize why).
> 
> A submit filter might be an option in some cases _BUT_ submit
> filters can only check the script but not the command line
> arguments (as far as I understand) and thus are generally only of
> very limited use - at least in my view.

No, torque can't do routing on "nodes" because it is far too complicated for
the simple min/max mechanism.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.supercluster.org/pipermail/torqueusers/attachments/20070830/b1965b99/attachment.bin


More information about the torqueusers mailing list