Allocate calls were using job table info in place after freeing mutex.
New logic copies data structures, frees mutex, sends message, and
then frees memory allocated for copy.

with SIGCONT.

requests can get backed up in a queue while the job actually completes).

some problems with slurmctld communication hangs.

away at any time anyway.

src/api/free_msg.c.

queued allocation request is satisfied. Srun just has a stub to catch
and log the message while using polling to notice the allocation has
been made.

structure.

DOWN or DRAIN state and not responding. Changed logic to clear NO_RESPOND
flag before proceeding with logic.

slurmctld restart).

reading job info.

Use it directly from  backfill plugin (instead of API call).

attempt failure (i.e. convert to event driven instead of just polling).
It does still have a 2-second timer to keep the overhead reasonable.

state saves, backfill scheduler runs, etc. when there was not a significant
state change that should trigger those events.

be changed whenever a node responded to a "ping" and other insignificant
events, which resulted in the backfill scheduling running more frequently
than required.

The plugin now gets passed the then current maximum priority to use as a
basis for setting the new job's priority (or not...).

Save and restore batch script's argc & argv across slurmctld restarts.

Convert all accessors to use exclusively pointers; this should fix many of the 64-bit incompatibility problems

Some of this was formerly in slurmctld/read_config.c.

purge the request and job if/when the node changes to state DOWN.

re-issuing it (reduces communications overhead).

KILL_JOB RPC to the slurmd, repeatedly if needed, but don't confirm it).
(gnats:326)

sent in a more timely fashion.

using node hostlist format.

for node registration, which is relatively rare).

primary and secondary controllers.