On 06/10/2014 04:16 PM, [email protected] wrote:
Pending and running jobs should be preserved across major releases too.
When we upgraded slurm from 2.5 to 2.6, it was tested before on a
working test cluster and all jobs were killed.
So, if I do an upgrade of slurm from 2.6.5 to 14.03., it should work on
a working cluster and it is not necessary to drain it? I just stop new
jobs, those that are already in queue (running or pending) should be
preserved?
Thanks,
Barbara
Quoting Barbara Krasovec <[email protected]>:
On 06/10/2014 08:24 AM, José Manuel Molero wrote:
Dear Slurm user,
Maybe this are dummy questions, but I can't find the response in the
manual.
Recently we have installed in a cluster, the slurm 14.03 version, in
a Red Hat/ Scientific Linux enviroment.
In order to tune the configuration, we want to test different
parameters of the slurm.conf
But there are several users running important jobs for several days.
How can I change the configuration of slurm and restart the
slurmctld without affecting to the users and the jobs of the users?
Its also necessary restart the slurm daemons?
Is also possible to upgrade or change the slurm version while there
are jobs running?
Thanks in advance.
Hello!
We apply new configuration parameters with "scontrol reconfigure"
(first I arrange new slurm.conf on all nodes).
Upgrading slurm: in my experience, when upgrading to a minor release
(e.g. from 2.6.4 to 2.6.X), it is not a problem to do it on a running
cluster, jobs are conserved. But upgrading to a major release (e.g.
from 2.5 to 2.6), cluster has to be drained first, otherwise jobs are
killed.
Cheers,
Barbara
