I’m trying to use RQS to limit the total number of slots which users can take
up on our cluster. This is slightly complicated by the hosts being split into
two groups, one for batch jobs (@compute) and one for interactive jobs
(@interactive). The idea would be that I’d limit the total slots taken up by a
user on the @compute set, but not restrict @interactive.
The RQS rule I’m using is:
{
name per_user_slot_limit
description "limit the number of slots per user"
enabled TRUE
limit users {*} hosts {@compute} to slots=16
}
However I don’t think this is generating the right effect. I think what this
is doing is saying that the limit of 16 slots applies on each of the individual
members of @compute, and not on the sum of the slots across all of @compute.
Can anyone suggest what the appropriate form of this rule would be to do what I
need? Would be variant below do anything different?
{
name per_user_slot_limit
description "limit the number of slots per user"
enabled TRUE
limit users {*} hosts {!@interactive} to slots=16
}
Thanks
Simon.
The Babraham Institute, Babraham Research Campus, Cambridge CB22 3AT Registered
Charity No. 1053902.
The information transmitted in this email is directed only to the addressee. If
you received this in error, please contact the sender and delete this email
from your system. The contents of this e-mail are the views of the sender and
do not necessarily represent the views of the Babraham Institute. Full
conditions at: www.babraham.ac.uk<http://www.babraham.ac.uk/terms>
_______________________________________________
users mailing list
users@gridengine.org
https://gridengine.org/mailman/listinfo/users
