Needed to change a couple of variables from 32- to 64-bit.

Add new burst_buffer.conf parameters: ValidateTimeout and OtherTimeout.
See man page for details.

previously take 2 restarts of the slurmdbd to make it stick correctly.

single-threaded cores.  A regression caused only 1 socket to be used on
this kind of node instead of all that were available.

Move the kvs_comm_set structure from src/api/slurm_pmi.h to
  src/common/slurm_protocol_defs.h so that we can move the
  free function into src/common also for cleaner logic.
bug 1670

bug 1670

Remove the individual message free calls scattered throughout the
  slurm code and use the slurm_free_msg_data() function instead.
bug 1670

Previous slurm_free_msg_data() function only supported a subset
  of RPC types.
bug 1670

If a job allocation returns some invalid contents, the pointer
  to the job structure may be NULL. This change preserves the error
  message and avoids a segv.

A bad (test) system left a bunch of long running jobs. This should
clean them up in a timely fashion.

If the backup dbd happened to be doing rollup at the time the primary resumed
both the primary and the backup would be doing rollups and causing contention on
the database tables. The backup would wait for the rollup handler to finish
before giving up control.

The fix is to cancel the rollup_handler and let the backup begin to shutdown so
that it will close an existing connections and then re-exec itself. The re-exec
helps because the rollup handler spawns a thread for each cluster to rollup and
just cancelling the rollup handler doesn't cancel the spawned threads from the
rollup handler. This cleans up the dbd and locks. The re-exec only happens in
the backup if the primary resumed and a rollup was happening.

Bug 1988

Fix case where if the backup slurmdbd has existing connections when it gives up control that the it would be killed.

If the backup had existing connections when giving up control, it would try to
signal the existing threads by using pthread_kill to send SIGKILL to the
threads. The problem is that SIGKILL doesn't go the thread but the main process
and the backup dbd would be killed.

when a cold-start (-c) happens to the slurmctld.

This was intended as a step toward managing jobs across mutliple
  clusters, but we will be pursuing a very different design.

Conflicts:
	src/sacct/options.c

from a user.

This would cause the slurmctld to cache the old default which wasn't valid
and cause the user to have to request the association always.

Conflicts:
	NEWS
	src/plugins/accounting_storage/mysql/as_mysql_job.c

bug 2009

Each node could have fewer tasks allocated on a node than the plane
  size, which broke the test. The plane size needs to be treated
  as a maximum consecutive rank value.

byg 2013