I use rpm's for our installs here. I usually pause all the jobs prior
to the upgrade, then I follow the guide here:
https://slurm.schedmd.com/quickstart_admin.html
I haven't done the upgrade to 18.08 though yet, and so I haven't had to
contend with the automatic restart that seems to be the
Thank you for your comments. I could potentially force the upgrade of the slurm
and slurm-slumdbd rpms using something like:
rpm -Uvh --noscripts --nodeps --force slurm-18.08.0-1.el7.x86_64.rpm
slurm-slurmdbd-18.08.0-1.el7.x86_64.rpm
That will certainly work, however the slurmctld (or in the ca
On Tuesday, 25 September 2018 9:41:10 PM AEST Baker D. J. wrote:
> I guess that the only solution is to upgrade all the slurm at once. That
> means that the slurmctld will be killed (unless it has been stopped first).
We don't use RPMs from Slurm [1], but the rpm command does have a --noscripts
We recently had a very good discussion on swap space and job suspension.
I had a look at the Intel pages on Optane memory.
https://www.intel.com/content/www/us/en/architecture-and-technology/intel-optane-technology.html
It is definitely being positioned as a fast file cache, ie for block
oriented d
On Tuesday, 25 September 2018 1:54:19 PM AEST Kevin Buckley wrote:
> Is there a way to rename a Reservation ?
I've never come across a way to do that, I've just had to delete and recreate.
Sorry Kevin!
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
Hello,
I wondered if I could compare notes with other community members who have
upgraded slurm on their cluster. We are currently running slurm v17.02 and I
understand that the rpm mix/structure changed at v17.11. We are, by the way,
planning to upgrade to v18.08.
I gather that I should upg
