[GE users] scheduler crashes on applying qrs for queued job?

Andreas.Haas at Sun.COM Andreas.Haas at Sun.COM
Tue Sep 18 16:39:53 BST 2007

On Mon, 17 Sep 2007, Reuti wrote:

>>> Resource quotas are targeting consumable and fixed complexes for now. 
>>> Making h_rt consumable is not really an option, but it would be possible 
>>> to define two queues on @pvmhosts with different user_lists set. The time 
>>> you set there (in the queue definition) for h_rt in one of them will also 
>>> be enforced. Maybe you have to limit the total slot count also in the 
>>> exechost definition, as you habe now (at least) two queues per machine.
>> I see no indication Henk actually made h_rt a consumable, so the case 
>> should work.
> This I missed here :-/ After arriving home and rethinking about it: wouldn't 
> this mean to have a limit per job what he requests?
>>>> limit        users testproject hosts @pvmhosts to h_rt=600

It is a static limit that is applied on all jobs of user testproject 
for the @pvmhosts. Though it is per job, but this is true for all 
non-consumable (= static) limits.

... only deficiency is that this limit is not (yet) enforced by execd's 
since resource quota limits generally are not propagated to execd during 
job delivery :-o

> All users in testproject using @pvmhosts may request in total h_rt=600, or as 
> {testproject} each user in this userlist. But a limit per job isn't 
> implemented up to now - or did I miss it? I filled:
> http://gridengine.sunsource.net/issues/show_bug.cgi?id=2147

As I understand it the #2147 jobs scope would aim on something 
different. The idea of

    limit        users testproject hosts @pvmhosts to h_rt=600

is just to apply -l h_rt=600 only on those jobs from user 
testproject. If h_rt were enforced it would allow to use different 
resource limits for different users. Though this can already be
done, but not without an additional queue.

> and (http://gridengine.sunsource.net/issues/show_bug.cgi?id=2148) some time 
> ago, which cover this.

I agree defining an allowed value range for each job is related 
to Henks use case, but #2148 goes beyond. Not sure how it could
be weaved in, but with consumable resources you may want to specify 
both a capacity and a value range. Maybe a new 'range' clause such 

    range        to mycomplex=(2,10,2)
    limit        hosts @pvmhosts to mycomplex=100

could be a solution for this. According your range definition 
#2148 it would mean jobs may request only 2, 4, 6, 8, or 10 
of mycomplex and for @pvmhosts there is a total mycomplex limit 
of 100.


To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net

More information about the gridengine-users mailing list