Bug 2314.

this happens anywhere in the code but just incase it ever does, lets fix
it.

This can be caused by a core reservation on nodes which get taken
  out of the system or fail.
bug 2296

Add "features_act" field (currently active features) to the node
    information. Output of scontrol, sinfo, and sview changed accordingly.
    The field previously displayed as "Features" is now "AvailableFeatures"
    while the new field is displayed as "ActiveFeatures".

cnodes can be reserved directly since 14.11. The plugin itself
printed warnings that it would be removed circa 15.08, following
through before 16.05.

Cray: Not running the Node Health Check after every job and step is now the
    default. Configure SelectTypeParameters with the NHC and/or NHC_STEP to
    run them.

salloc/sbatch/srun did not mention this. Also reference OverTimeLimit
as another option affecting the final run time. Bug 2309.

the job starts update the cpus_per_task appropriately.

This also moves update num_tasks to after the setting of node counts on
an update.  It didn't appear to matter, but the cpus_per_task and
pn_min_cpus had to be figured out after the cpus and nodes were set but
before tasks.

Bug 2302

Add an "scontrol top <jobid>" command to re-order the priorities of a user's
    pending jobs. May be disabled with the "disable_user_top" option in the
    SchedulerParameters configuration parameter.
bug 1133

burst_buffer/cray - Improve tracking of allocated resources to handle race
    condition when reading state while buffer allocation is in progress.
Also initialize a mutex

DBD for the first time.  The corruption is only noticed at shutdown.

Bug 2293

Set job's reason to "Priority" when higher priority job in that partition
    (or reservation) can not start rather than leaving the reason set to
    "Resources".
bug 2285

The partition-specific SelectTypeParameters parameter can now be used to
    change the memory allocation tracking specification in the global
    SelectTypeParameters configuration parameter. Supported partition-specific
    values are CR_Core, CR_Core_Memory, CR_Socket and CR_Socket_Memory. If the
    global SelectTypeParameters value includes memory allocation management and
    the partition-specific value does not, then memory allocation management for
    that partition will NOT be supported (i.e. memory can be over-allocated).
    Likewise the global SelectTypeParameters might not include memory management
    while the partition-specific value does.
bug 2239

error message.

If a reservation's nodes value is "all" then track the current nodes in the
    system, even if those nodes change. Nodes will automatically be added to
    or removed from a reservation when slurm.conf changes.
bug 2204

Bug 2281

Rename the variable to match rest of codebase while here. This is related to
bug 2295, although snprintf() protects against buffer overflow in 15.08 and up.

Later releases have switched over to snprintf to avoid this issue, but 14.11
did not get that patch. Bug 2295.

Burst buffer advanced reservation units treated as bytes (per documentation)
    rather than GB.

time.

static/overlap systems when some hardware issue happens when restarting
the slurmctld.

a dynamic system and mark the block in error on a static/overlap system.

Bug 2273

Don't use lower weight nodes for job allocation when topology/tree used.
bug 2284

Preemption/gang scheduling: If a job is suspended at slurmctld restart or
    reconfiguration time, then leave it suspended rather than resume+suspend.
bug 2274

task/affinity: Disable core-level task binding if more CPUs required than
    available cores.
bug 2267

Log as error if more than 3 aeld connects per second that cause is
  likely duplicate slurmctld daemon
bug 2278

This is needed to properly enforce limits and account for usage.

Change default CgroupMountpoint (in cgroup.conf) from "/cgroup" to
    "/sys/fs/cgroup" to match current standard.
For details, see https://wiki.freedesktop.org/www/Software/systemd/PaxControlGroups/