while the cluster is down. The cluster will figure out what changed
after starting up or after resuming from using the cache.

When the controller starts up and the dbd is not up it waits until the
dbd comes up. At this point, the controller needs to find out if
anything has changed in the federation (e.g. other clusters or self
removed from cluster).

When a non-origin cluster is removed:
- running jobs remain - fed_details removed so it can't call home.
- origin cluster removes tracking job for running jobs
- pending jobs are removed.
- pending srun/sallocs don't get notified.
- other clusters remove removed cluster from viable and active sibs

When an origin cluster is removed:
- all pending jobs are removed from all clusters that had job.
- pending srun/sallocs are notified of termination
- running jobs remain.

The SLURM_ID_HASH used for Cray systems has changed to fully use the
entire 64 bits of the hash.  Previously the stepid was multiplied by
10,000,000,000 to make it easy to read both the jobid as well as the
stepid in the hash separated by at least a couple of zeros, but this
lead to overflow on the hash with steps like the batch and extern step
where they used all 32 bits to represent the step.  While the new method
ruins the easy readability it fixes the more important overflow issue.
This most likely will go unnoticed by most, just a note of the change.

# Conflicts:
#	NEWS

Bug 3919

bug 3757

more than 1 partition or when the partition is changed with scontrol.

Bug 3849

submitted to a QOS/association.

Bug 3849

Continuation of b9719be2

CID: 170772, 170773
Introduced by commit: 250378c2

Correct error message when ClusterName in configuration files does not match
    the name in the slurmctld daemon's state save file.

the requested value, instead of always setting one.

This would make --hint=multithread not work at all.

See Bug 3855 (commit 3c852da1)

Issue originated from commit 82a959a8.

Since you can no longer get into the code without there being a buffer there is
no reason to check it.

Correct error message when ClusterName in configuration files does not match
    the name in the slurmctld daemon's state save file.

Bug 3526

Bug 3526

There was a bug in the heterogeneous job work (fixed now) that resulted
  in a bunch of jobs without time limits from being killed. This patch
  prevents those jobs from running indefinitely.

Bug 3502.

files on startup.  The new default behavior is to 'fatal' if state files
are bad.  This flag is to avoid that fatal if you expect things to be bad.

This commit just adds the flag but doesn't do anything more than that.

the requested value, instead of always setting one.

This would make --hint=multithread not work at all.

See Bug 3855 (commit 3c852da1)

Issue originated from commit 82a959a8.

bug 3447