I think the user is saying that they want CMS.A to get the first crack at the resources
regardless of fairshare as well.. this is the second CMS facility in recent months that wants to do that. To do this you can set the priority halflife to a very long value so that the effective priority doesn't go up after they have run a long time.. But in addition you would have to set the GROUP_PRIO_FACTOR of the atlas group high as well. Steve Timm From: HTCondor-users [htcondor-users-bounces@xxxxxxxxxxx] on behalf of Brian Bockelman [bbockelm@xxxxxxxxxxx]
Sent: Monday, June 29, 2015 1:11 PM To: HTCondor-Users Mail List Subject: Re: [HTCondor-users] priority fo special user Hi Jiang,
The groups are independent of the individual user fairshare. In addition to giving cms.A the best priority, you’ll want to make sure that group CMS has the largest quota.
I think you want to look at the GROUP_QUOTA_* knobs here:
http://research.cs.wisc.edu/htcondor/manual/v8.3/3_4User_Priorities.html#SECTION00447000000000000000
One way to set things up is something like the following:
GROUP_QUOTA_DYNAMIC_cms = .99
GROUP_QUOTA_DYNAMIC_atlas = .01
GROUP_ACCEPT_SURPLUS = true
then to adjust the priority factor of cms.A appropriately.
Brian
|