HI,

Am 15.07.2011 um 09:16 schrieb Christian Goll:

> is there a way to limit the number of jobs from the users per queue. The
> scheduler variable maxujobs can only be set global. With user limits
> only the number of slots can be limited or is there a secret option I
> missed?

it's necessary to define a new consumable which you could name just "jobs" and 
has as a consumable resource by "JOB" (instead of "yes", hence it will be 
consumed only one time per job, independent from the number of requested slots) 
and a consumption of 1 per job which you also define there.

Then an arbitrary high number of this resource need to be attached on a global 
level, so that this limit will never be enforced: `qconf -me global` 
(complex_values jobs=999999).

Next step is to define an RQS to limit this resource per user, group, queue... 
whatever you like. And you are done.

Pitfall: it's not possible to make a consumable resource "requestable = NO", 
hence a cheeky user could define it to request "-l jobs=0" and always slip in. 
But you can set up a JSV to catch and correct this to be just 1 all the time.

-- Reuti


> In our actual setup we have the maxujobs set to 10 in order to animate
> the users to start less jobs but with more cores. Now we want to add a
> cluster for serial/small jobs, but do not want to get our parallel
> cluster flooded with small jobs.
> 
> kind regards,
> Christian
> 
> -- 
> Dr. Christian Goll
> HITS gGmbH
> Schloss-Wolfsbrunnenweg 35
> 69118 Heidelberg
> Germany
> 
> phone: +49 - 6221 - 533 230
> email: [email protected]
> _______________________________________________
> users mailing list
> [email protected]
> https://gridengine.org/mailman/listinfo/users


_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users

Reply via email to