[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Job attribute based preemption

MaxJobRetirementTime is useful for controlling how long the existing job is allowed to run once it is preempted. To control whether the existing job gets preempted or not, I would suggest using a combination of RANK and START expressions. For example, the START expression can look at attributes of the existing job (published into the machine ClassAd via STARTD_JOB_EXPRS) to decide whether it is acceptable to preempt the existing job.


Horvátth Szabolcs wrote:


I disabled preemption altogether in our pool but would like to enable it for only a specific type of job. I'm currently using the rank expression to order the execution of the jobs and have user priority effect only within these job types but would like to have very important jobs that do preempt others (but not each other). I thought that by using an expression for the MaxJobRetirementTime I could control preemption based on job classad attributes but I'm not sure how to compare the attributes of the currently running job to the new job to decide whether preemption should happen.

Is it possible at all what I'd like to do or do I have to use a completely different method to achieve
job attribute based preemption?


Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at either