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

Re: [Condor-users] PREEMPT


PREEMPT is not published in the ClassAd by default, so it is expected that you won't see it there.

However, your use of PREEMPT might not be what you really want. The PREEMPT expression specifies when the startd should preempt the current running job (e.g. because other non-condor activity has higher priority on the machine). Preemption between Condor users is a different matter entirely. There are various policy expressions that can control this behavior, but the chief ones that come to mind are PREEMPTION_REQUIREMENTS and MaxJobRetirementTime.

Let me know if you need further details to get the policy you want.


On Mar 1, 2006, at 8:55 AM, Steven Timm wrote:

I have 5 nodes of a much larger pool on which I want
to enable pre-emption for jobs of a certain group of user.

I thought this could be done by adding the following to

PREEMPT =  (agroup == "group_e740")
(where agroup is a classad attribute which is automatically set
in all jobs that are submitted by this user),

But when I do condor_status -long on the node in question,
I don't see the PREEMPT argument come back. In fact I don't see any
preempt fields in any of the machine classads in my pool.
Am I doing something wrong?  If so, what?


Steve Timm

Steven C. Timm, Ph.D (630) 840-8525 timm@xxxxxxxx http://home.fnal.gov/~timm/ Fermilab Computing Div/Core Support Services Dept./Scientific Computing Section
Assistant Group Leader, Farms and Clustered Systems Group
Lead of Computing Farms Team
Condor-users mailing list