[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Spawning jobs depending on system load and start_delay, start_count
- Date: Wed, 18 Nov 2009 11:08:24 -0500
- From: Jason Stowe <jstowe@xxxxxxxxxxxxxxxxxx>
- Subject: Re: [Condor-users] Spawning jobs depending on system load and start_delay, start_count
You can also use the setting START_LOCAL_UNIVERSE. By default, this
START_LOCAL_UNIVERSE = TotalLocalJobsRunning < 200
Unfortunately, you don't have access to CPU load in the scheduler ad,
but you could figure out how many of these jobs you want, say 8, and
change the policy to:
START_LOCAL_UNIVERSE = TotalLocalJobsRunning < 9
Condor checks this policy with the job's Requirements expression, and
starts it if they are both true.
Jason A. Stowe
Cycle Computing, LLC
Leader in Condor Grid Solutions
Enterprise Condor Support and Management Tools
On Tue, Nov 17, 2009 at 10:14 PM, Matthew Farrellee <matt@xxxxxxxxxx> wrote:
> Heiko Burghardt wrote:
>> Actually, this works fine for queuing the jobs in general. But we like
>> to combine this feature with a load dependency rule in Condor, means:
>> stop to run jobs at a load higher than value X. That's where I fail as
>> the UWCS_START, UWCS_SUSPEND, ... rules do not seem to work in the local
>> universe. Using e.g. the scheduler universe the situation is visa verce:
>> load dependency works (with some restrictions) but there is no
>> restriction in number of jobs in a time frame.
>> Does somebody have an idea on how to set up Condor for our requirements?
> Have you considered running a condor_startd next to your condor_schedd? That can get you both types of policy.
> A little known feature of the Schedd even provides you a way to skip using a Collector and Negotiator.
> 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: