[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] FetchWorkDelay -- how can I tell if it's working?
- Date: Tue, 2 Mar 2010 23:20:14 -0500
- From: Ian Chesal <ian.chesal@xxxxxxxxx>
- Subject: Re: [Condor-users] FetchWorkDelay -- how can I tell if it's working?
Got it. Needed to a full startd restart, not just a reconfig. Now it
has ceased to run my hook script when a node has a job on it.
I really wish there was a list of settings that require restarts vs.
settings that just require reconfigs...
On Tue, Mar 2, 2010 at 9:44 PM, Ian Chesal <ian.chesal@xxxxxxxxx> wrote:
> I absolutely, positively do not want Condor to run my hook script if a
> slot is Claimed and not Idle. I've got:
> FetchWorkDelay = ifThenElse(State == "Claimed", ifThenElse(Activity ==
> "Idle", 0, 4838400), ifThenElse(State == "Unclaimed" && Activity ==
> "Idle", 0, 1200))
> I've seeded my machines with long (12 hour) sleeper jobs to test this.
> But I'm still seeing the Startd fire my hook script at bizarre
> intervals. Nothing periodic at all, it's all over the place: 5
> minutes, 12 minutes, 7 minutes, 13 minutes...
> How can I tell if Condor is delay the fetch work call appropriately?
> I've got ALL_DEBUG=D_FULLDEBUG on but the StartLog doesn't mention the
> delay time, just when it runs the fetch work hook for me.
> - Ian