Start a job in the highest priority partition possible, even if it requires
preempting other jobs and delaying initiation, rather than using a lower
priority partition. Previous logic would preempt lower priority jobs, but
then might start the job in a lower priority partition and not use the resources
released by the preempted jobs.
bug 1032

Previously job would only run in first listed partition.

Fix gang scheduling for jobs submitted to multiple partitions.
Previous logic assumed the job's "partition" field contained a
single partition name, that in which the job is running. That
was recently changed in order to support job's being requeued,
which we want to be runable in all of it's valid partitions.

signal 1.

done for normal steps.

of acting like it is a signal and exitcode.

previous it was always -2.

Apply BatchStartTimeout configuration to task launch and avoid aborting
srun commands due to long running Prolog scripts.
bug 978

When nodes scheduled for reboot, set state to DOWN rather than FUTURE so
they are still visible to sinfo. State set to IDLE after reboot completes.
bug 1007

"job_comp/mysql" setting an incorrect default database.

database index for the array elements avoiding duplicate database values.

job elapsed time.

the i/o thread.

exit code.

information wasn't stored in accounting.

job/step completion.

bit_unfmt.

Signed-off-by: Danny Auble <da@schedmd.com>

HealthCheckProgram for nodes in any other states than IDLE.#978

Unload job tables rather than windows at job end. The table unload
also unloads job tables.

lost should the slurmctld restart.

Correct NumCPUs count for jobs with --exclusive option.
bug 909

This probably only happens on native Cray systems due to the
deallocation delays related to node health check. In any case,
the symptom is error message of this sort "job # dealloc of node
... bad node_offset 0 count is 0". It then fails to deallocate
the nodes GRES back for use by other jobs.
bug 973

slurm_conf_reinit.

counting as multiple nodes.

slurmstepd attempts to create it, for example left over from a previous
requeue or crash, delete it and recreate it. #961.