Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] Limiting number of jobs of specific user to N per node
- Date: Mon, 23 Oct 2017 17:21:23 +0000
- From: Michael Pelletier <Michael.V.Pelletier@xxxxxxxxxxxx>
- Subject: Re: [HTCondor-users] Limiting number of jobs of specific user to N per node
> -----Original Message-----
> From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf
> Of Greg Thain
> Sent: Monday, October 23, 2017 9:51 AM
> To: htcondor-users@xxxxxxxxxxx
> Subject: [External] Re: [HTCondor-users] Limiting number of jobs of
> specific user to N per node
>
>
> Machine custom resources are the best way to do this. On the execute
> side, you can define how many resources that machine has, in some
> arbitrary unit, like this:
>
> MACHINE_RESOURCE_Belle = 4
>
> and in the job ad, the belle jobs should say
>
> Request_belle = 1
>
> which means "only match to machines which have 1 or more belle resources
> remaining, and consume 1 for the duration of my job".
>
> -greg
> _______________________________________________
Is there any way to specify a resource which a job needs to have available in order to start up, but does not need to hold for the duration of the job? Or is that a feature request? :)
-Michael Pelletier.