Dear Jette,
Thanks :-) Yeah, preserving running jobs is not important, but not having
to create a completely new user data base and accounts would be very
useful. It seems that that should work without problems, then.
Cheers,
Mikael J.
http://www.iki.fi/~mpjohans/
On Fri, 31 Oct 2014, je...@schedmd.com wrote:
welcome to the 21st century.
if you want to avoid losing pending jobs, upgrade from v2.2 to v2.4, then to
v2.6, then to v14.11. I doubt that running jobs would be preserved. For more
information, see
http://slurm.schedmd.com/quickstart_admin.html#upgrade
Quoting Mikael Johansson <mikael.johans...@iki.fi>:
Hello All,
We have a power-out soon on our cluster, and I thought now would be a good
opportunity to update SLURM. Just three quick questions to ease my mind:
1. Is an upgrade from version 2.2.7 to 14.03 expected to work "in-place"
without problems, that is, without loss of the user database and major
settings? In case it makes a difference, it would mean an upgrade from
the official package supported version 2.2.7 on Scientific Linux 6.3 to
a self-compiled version of SLURM.
2. Is there a need to upgrade any of the other packages in order to get
version 14 working properly (thinking of MUNGE and MySQL, but perhaps
there's other non-obvious dependencies as well)?
3. Is version 14.03.9 the version to go for, or would people recommend
14.11.0-pre5 instead?
Thanks in advance, happy Halloween,
Mikael J.
http://www.iki.fi/~mpjohans/
--
Morris "Moe" Jette
CTO, SchedMD LLC
