Am 21.06.2012 um 12:07 schrieb Dave Love:
> Reuti <[email protected]> writes:
>
>> In principle yes, but sometimes jobs just won't start in certain conditions
>> of defined RQS - it's a bug. Just check, whether it's working for your setup.
>
> Is that in the existing issues list, and could we add an example if not?
The problem is to have an example that won't work for sure. The last thing I
tried was:
{
name long
description Long limits
enabled TRUE
limit name slots users {*} queues serial_long,parallel_long to
slots=72
}
{
name general
description General SGE limits
enabled TRUE
limit name login queues login hosts {*} to slots=1
limit name short queues short hosts {*} to slots=2
limit name slots hosts {*} to slots=8
}
But then jobs won't start. Instead I have to define the slot count in the
exechost definition and set the second RQS to FALSE. With the effect, that a
login queue to check the job state won't be available any longer, like the
queue for short jobs (with intended oversubscription) too.
Setting the first RQS to FALSE and the second for TRUE would also work, but
then I couldn't limit the number of long running jobs per user.
-- Reuti
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
