and may have been exhausting virtual memory, resulting in the death of
slurmctld.

the left-over slurmctld process on abnormal termination.

clarity. No change in functionality or logic.

If the "-c" option is not specified then only the jobs and some node
state information will be preserved. Specifically the state of DOWN,
DRAINED, or DRAINING nodes and the associated reason field for those nodes.

1=required nodes DOWN/DRAINED.

unavailable states).

right away (before running scheduling function).

returned to service. The priority is changed from 1 to value which would
be set for the job if submitted at that time.
(gnats:279)

nodes which are not available (DOWN or DRAIN). This will prevent them from
blocking other jobs from using the nodes which are available (i.e. over-ride
FIFO scheduling).
(gnats:279)

Without doing so, its internal record of jobs from its last period of
activity are resurrected.

MAX_SERVER_THREADS is exceeded. Thread counter, mutex, and cond
logic all moved into new allocate/deallocate server thread functions.

assumes control. It previously captured state only when the backup
controller daemon was initiated.

This was not happening for the backup slurmctld.

   setting SLURM_NODELIST in the environment)

in slurmd killing itself if the KILL_JOB RPC arrived before the job began
execution (the pid in the data structure was still zero.

cases. Exit code is now 0 only if all commands execute without error.
Exit code is 1 if any failure occurs for any command executed.
(gnats:278)

when the job does not exist).

it is a duplicate record.

 o check for a job step state of STARTED before issuing kill_job rpc

was only going to 65500 for the job_id and the step_id was always zero.
This change does not elimiate the possibility of an error, but reduces
its probability by a factor of about 65000.
(gnats:276)

to job_kill request and slurmctld leaves node and job in COMPLETING state
until the slurmd issues an EPILOG_COMPLETE RPC on each node. This permits
better support for non-killable processes and/or long-running epilog scripts.
Several minor changes in node registration handling and slurmctld agent
logic to better address a flood of incomming RPC (typically when system
restarts).
(gnats:268)