Am 20.06.2012 um 10:00 schrieb William Hay:
> On 25 May 2012 13:26, Reuti <[email protected]> wrote:
>> I'm on vacation again and will look into it on June 1st after my return.
>>
>> Just to let you know, that it's not forgotten - Reuti
> Hi Reuti,
> did you have occasion to check this out? The recent comments about
> multi limit RQS being buggy may explain why I haven't been able to
> determine this experimentally.
I remember something like this:
reuti@pc15370:~> qstat
job-ID prior name user state submit/start at queue
slots ja-task-ID
-----------------------------------------------------------------------------------------------------------------
4302 6.00000 test.sh reuti r 06/21/2012 18:04:44 all.q@pc15381
1
4303 0.00000 test.sh reuti qw 06/21/2012 18:04:44
1
reuti@pc15370:~> qquota
resource quota rule limit filter
--------------------------------------------------------------------------------
boolean/excl exclusive=1.000000/2 users reuti
reuti@pc15370:~> qconf -srqs
{
name boolean
description NONE
enabled TRUE
limit name excl users reuti to exclusive=2
}
But it's not working right now, the waiting job sees:
scheduling info: cannot run because it exceeds limit "/////" in rule
"boolean/excl"
The ouput "/////" could be more descriptive.
-- Reuti
> Thanks
>
> William
>>
>>
>>
>> Am 22.05.2012 um 12:04 schrieb William Hay:
>>
>>> On 27 February 2012 15:43, Reuti <[email protected]> wrote:
>>>> Am 27.02.2012 um 16:18 schrieb William Hay:
>>>>
>>>>> On 26 February 2012 12:41, Reuti <[email protected]> wrote:
>>>>>> Am 26.02.2012 um 12:32 schrieb William Hay:
>>>>>>
>>>>>>> On 26 February 2012 09:13, mahbube rustaee <[email protected]> wrote:
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> How can prevent some users to use some resource with -l option ? JSV
>>>>>>>> is best
>>>>>>>> way for that ?
>>>>>>>>
>>>>>>>> Thx
>>>>>>> If it is a consumable you could could try configuring a quota of 0 for
>>>>>>> them.
>>>>>>
>>>>>> Good idea, it will work for exclusive too, as the internal
>>>>>> representation is an integer value.
>>>>> Is that (applying quotas to exclusive resources) actually known to
>>>>> work/documented behavior/supported by one of the forks?
>>>>
>>>> For me it's working in 6.2u5. Was this "feature" removed by one of the
>>>> forks. I recall a former discussion about the internal representation of
>>>> an exclusive attribute and using it for a quota, but can't find it for now.
>>>>
>>> Resurecting old thread time. Do you know the rate of consumption for
>>> exclusive resources? The consumable attribute is yes which normally
>>> implies per slot consumption but my exclusive
>>> resources claim to have exactly one unit available so that wouldn't
>>> work. The "obvious" rate of consumption would be 1 per host (or per
>>> queue instance for exclusive resources associated with a queue)
>>> Presumably jobs that don't request exclusive access don't consume any
>>> of the resource (I know grid engine keeps a separate count of usage by
>>> non-exclusive jobs for exclusive resources).
>>>
>>> William
>>
>>
>>
>
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
