[Condor-users] Changing the time interval for matching

[Stephen McGough <stephen.mcgough@xxxxxxxxxxxxxxx>]

Dear All,

We have successfully set up a cluster which uses a non Condor method for sleeping Windows 7 computers and uses Rooster to wake up these computers when jobs are waiting. However, we now have a race condition. The University here have a tight requirement for shutting down computers "out of hours" and if no Condor job starts within 5 minutes the computer will be powered down. We have also seen that it can take Condor 5 minutes to match and start a job on a computer once Rooster has woken it up. At the moment we're seeing a number of jobs which wake a computer up, fail to start in 5 mins so the computer goes to sleep, just to wake up another computer. All jobs now run but it would be good to remove these unwanted wake-ups.

To do this we would like to reduce the amount of time Condor takes to match (we're trying to extend the time interval before a computer sleeps too). The START expression evaluates directly to true "out of hours".

Does anyone know what other expressions need to be set to smaller values to get Condor to have a quicker turn-around?

Many thanks,

Steve..