Note that some parameters require a full restart, not just reconfigure. There's little user impact when restarting slurmctld.
When you get to upgrading have a look at this: http://slurm.schedmd.com/quickstart_admin.html#upgrade M On Tue, Jun 10, 2014 at 7:16 AM, <[email protected]> wrote: > > Pending and running jobs should be preserved across major releases too. > > > 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 > > -- Hey! Somebody punched the foley guy! - Crow, MST3K ep. 508
