Re: [Condor-users] kill exprs with job props

[Douglas L Thain <dthain@xxxxxxxxxx>]

In light of this exchange, I want to refine my question.  :)

I want to do something like this:
PREEMPT = ( if suspended ) && ( suspend time > JobMaxSuspend )
Where JobMaxSuspend is defined in the *job's* classad.

Different users have different tolerances for suspension,
so changing the machine's default suspend time doesn't help me.

Is there any hidden difficulty here?

The only wrinkles that I see are:

A - Users may decline to define +JobMaxSuspend=n in their submit files.
    This can be addressed by adding to SUBMIT_EXPRS in the local environment.
    Flocked users will run into trouble if they haven't defined it.

B - Users can "cheat" by defining arbitrarily long JobMaxSuspend times.
    To solve this, we need max() and min(), which require ?: conditionals
    from NewClassAds.  However, the effects of such "cheating" are
    minimal (swap space and a few pids consumed) and can be monitored
    administratively.

Did I get that right, or is there something else to worry about?

Cheers - Doug


On Mon, 5 Dec 2005, Derek Wright wrote:

>
> On Mon, 5 Dec 2005 09:48:26 -0600  Erik Paulson wrote:
>
> > > Is KILL evaluated in the context of the running job's ClassAd?
> > >
> >
> > No, it's in the machine ad.
>
> lies, all lies.  KILL, like all startd policy expressions, is
> evaluated in the context of *both* the machine ad *and* the running
> job's ad.  that's why you don't have to do anything special to refer
> to the job universe, imagesize, etc, in the default policy
> expressions.  if you're talking about an attribute that happens to be
> in both the machine and job classad, and therefore need to use classad
> scoping, "MY.foo" is the "foo" attribute from the machine ad, and
> "TARGET.foo" is the "foo" attribute from the currently running job.
>
> > Export JobMaxSuspend into the machine ad with STARTD_JOB_EXPRS
>
> that's only if you want to see the current value of JobMaxSuspend in
> the machine's classad for the purposes of condor_status, etc.
>
> enjoy,
> -derek
>
>
>
> _______________________________________________
> Condor-users mailing list
> Condor-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>