in slurmctld.h which is included by slurm_accounting_storage.h which is
included by slurmdbd.c which would cause confusion at the very least.

to avoid it thinking we don't have a cluster name.

Previously there was a sleep(5) during which the backup controller
was non responsive during its startup mode or returning from primary
mode.

This will prevent possible confusion for the backup controller
when it switches from primary back to backup modes since those
pthread IDs are no longer value. Note the thred_id_rpc could be
used by the backup controller after returning to backup mode

they are coordinators over.

If there are completing jobs, a reconfigure will set wrong job/node
state: all nodes of the completing job will be set allocated, and the
job will not be removed even if the completing nodes are released. The
state can only be restored by restarting slurmctld after the completing
nodes released.

-> 2.6 slurmd

could end up before the job started. Bug 371

We now reject jobs with an invalid accounting frequency at
submit time rather than launch time, so the error is slightly
different and the test needs to change for that.

This avoids waiting for the job's initiation to fail.

Only cancel the job.

Fix job state recovery logic in which a job's accounting frequency was
not set. This would result in a value of 65534 seconds being used (the
equivalent of NO_VAL in uint16_t), which could result in the job being
requeued or aborted.