interval.

merged together.

sacct.

Add support for SchedulerParameters value of bf_max_job_start that limits
the total number of jobs that can be started in a single iteration of the
backfill scheduler.
bug 607

bug 607

placed.

count.

nodes.

If a job requires specific nodes and can not run due to those nodes being
busy, the main scheduling loop will block those specific nodes rather than
the entire queue/partition.
bug 595

is not a corresponding association.

is not a corresponding association.

needed to forward a message the slurmd would core dump.

describing that jobs must be drained from cluster before deploying
any checkpoint plugin.

Properly enforce a job's cpus-per-task option when a job's allocation is
constrained on some nodes by the mem-per-cpu option.
bug 590

bug 586

Set GPU_DEVICE_ORDINAL environment variable.

Previous logic would try to pick a specific node count and on a
heterogeneous system, this would cause a problem. This change
largely reverts commit a270417b

i.e. salloc -n32 doesn't request the number of nodes and with the previous
code if this request used 4 nodes and only 1 was left in GrpNodes it
would just run with no issue since we were checking things before we
selected how many nodes it ran on.

Now we check this afterwards so we always check the limits on how many
nodes, cpus and how much memory is to be used.

Fix step allocation when some CPUs are not available due to memory limits.
This happens when one step is active and using memory that blocks the
scheduling of another step on a portion of the CPUs needed. The new step
is now delayed rather than aborting with "Requested node configuration is
not available".
bug 577