Re: [Condor-users] Getting certain jobs to avoid eachother

[Martin Steele <paw_deer@xxxxxxxxxxx>]

My sentiments exactly. I don't want my AntisocialJobs to sit idle if there are facilities available, but to just avoid eachother as much as possible. If I can also define a cap on the number of such jobs that an execute host is willing to serve then that would help too.

M

---

From: Dimitri Maziuk <dmaziuk@xxxxxxxxxxxxx>
To: condor-users@xxxxxxxxxxx
Sent: Monday, 12 December 2011, 18:45
Subject: Re: [Condor-users] Getting certain jobs to avoid eachother

On 12/12/2011 12:21 PM, Nathan Panike wrote:
> On Mon, Dec 12, 2011 at 05:49:34PM +0000, Martin Steele wrote:
>> Hi,
>>
>> I have a class of jobs that I'd like to ensure is maximally dispersed amongst
>> my pool's resources. What marks these jobs out from others is that they
>> require a lot of memory, but let's consider the generic problem of having a
>> particular class of jobs avoiding eachother. Firstly, I'll get these jobs to
>> identify themselves by setting a custom classad value in their submit script,
>> e.g. via:
>>
>> +AntisocialJob = True
>
> How about adding the _expression_
>
> TARGET.SlotID == 1
>
> to your Requirements _expression_? Then at most one "antisocial" job would run on
> a given machine at a single time.

However, it won't run on a machine where slot 1 is already occupied by
some other job. Which may or may not be ok.

--
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu


_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/condor-users/