Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Job attribute based preemption
- Date: Tue, 03 Apr 2007 18:37:04 +0200
- From: Horvátth Szabolcs <szabolcs@xxxxxxxxxxxxx>
- Subject: Re: [Condor-users] Job attribute based preemption
Hi Dan,
But I do have to lower the MaxJobRetirementTime if I want to make the
preemption instantaneous, don't I?
If I only modify the start expression I get the preemption happening
(actually almost all of my running jobs
are already preempted because of the rank expression we use) but it is
not instant.
Cheers,
Szabolcs
Dan Bradley wrote:
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.
--Dan