It's have of MessageTimeout with a minimum of 1 sec, and maximum of 4
secs with the idea that we don't want to keep live users waiting for
long. In job_scheduler.c:
sched_timeout = slurm_get_msg_timeout() / 2;
sched_timeout = MAX(sched_timeout, 1);
sched_timeout = MIN(sched_timeout, 4);
Quoting Paul Edmon <[email protected]>:
One more question, what controls the maximum runtime for the Main Scheduler?
-Paul Edmon-
On 04/11/2014 03:02 PM, Paul Edmon wrote:
Thanks. That's helpful.
-Paul Edmon-
On 04/11/2014 03:00 PM, [email protected] wrote:
In defer mode, the main scheduling loop runs once per minute, but
most of your jobs will typically be scheduled by the backfill
scheduler instread (although that depends upon your
configuration). The backfill scheduler typically test far more
jobs since it can periodically reliquish locks to let other RPCs
be processed, while the main scheduling loop just gives up after a
few seconds. Use SchedulingParameters=bf_interval=#,... to specify
the frequency at which the backfill scheduler runs.
I'll make the main scheduling loop frequency configurable in the
next release, but today it is not configurable without changing
the code. See the variable PERIODIC_SCHEDULE in
src/slurmctld/slurmctld.h if you care to change the frequency today.
Quoting Paul Edmon <[email protected]>:
So if you are running in defer mode for the scheduler what
determines the frequency of the main loop for the scheduler? Can
this be changed?
-Paul Edmon-