Subject: Re: [Condor-users] Master scheduling Intervals for debugging
Ashley, The problem you are having is a result of the settings for the negotiation cycle that Condor uses to match submittor's jobs with startds available to run them. You can use NEGOTIATOR_CYCLE_DELAY and NEGOTIATOR_INTERVAL to specify the mandatory wait time in between negotiation cycles, which defaults to 20 seconds I think, and the interval that negotiation cycles are started, which I think defaults to negotiate every 300 seconds.
condor_reschedule also works, but on large pools/busy schedulers, it doesn't necessarily make things more efficient. When new jobs are submitted, and equivalent reschedule generally occurs.
Hope this helps,
Jason
--
=================================== Jason A. Stowe
On 8/20/07, Mills, Ashley, VF-Group <
Ashley.Mills@xxxxxxxxxxxx> wrote: > I am having a daymare (as opposed to a nightmare) getting my scripts to > execute without errors. I would like to debug what is going on, but
> there is a huge delay between submitting a job, and when it starts > running (perhaps 10 minutes). > > I am assuming this is because some interval on the master is set to a > large value. I understand this would be convenient for most everyday
> usage scenarios, but for debugging purposes I'd like the jobs to be sent > to the machines instantly. I've looked in condor config but I can't see > which parameter to change. Can you tell me?
> > Thanks > > Ashley Mills > > _______________________________________________ > Condor-users mailing list > To unsubscribe, send a message to
condor-users-request@xxxxxxxxxxx with a > subject: Unsubscribe > You can also unsubscribe by visiting > https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> > The archives can be found at: > https://lists.cs.wisc.edu/archive/condor-users/ >
![[Computer Systems Lab]](https://www-auth.cs.wisc.edu/pics/csl_logo.gif){kind=logo}