On Thu, Jun 09, 2016 at 05:53:35PM +0200, R??my Dernat wrote: > Hi, > I am working on a way to prioritize jobs from some users on some specific > queues. I know it can be done, but I do not know exactly how. AIUI grid engine has a single notion of priority for the whole cluster and as far as access to specific resources (like queues/hosts) are concerned users/projects either have access or don't. Given that grid engine jobs can run in multiple queues/hosts simultaneously the obvious alternative would be deadlocks.
If I'm reading your intent correctly I would create a special project for these
users with higher priority and then block it from running in all queues bar
test.q.
When the users want their higher priority they can request the project
in question and be forced into the test.q by it.
> I saw that there's already "weight_user", but this value, combined with
> others must not exceed "1".
> Correct me if I am wrong, but the best way is to create a userset for
> these users and then apply a resource quota on it:
> e.g.:
> {
> name powerusers_on_testqueue
> description "limit the priority for queue test.q for all users except
> for powerusers"
> enabled TRUE
> limit users {!@powerusers} queues {test.q} to weight_user=0.15
> }
The above won't work because the resources controlled by RQS are grid engine
complexes
and weight_user is a scheduler configuration parameter not a complex.
> would be prioritize over other users. There is also the fshare value on
> userset which could be modified.
I don't think there is an fshare for userset only for departments(a special
mutually exclusve variant of usersets) and projects.
William
signature.asc
Description: Digital signature
_______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
