Ole Holm Nielsen via slurm-users <slurm-users@lists.schedmd.com> writes:
> Hi Bjørn-Helge, > > On 3/7/25 08:59, Bjørn-Helge Mevik via slurm-users wrote: >> My 2¢: >> If upgrading the deb packages does *not* restart the services, then >> you >> can just upgrade all the slurm packages on the controller, then restart >> slurmdbd first and slurmctld afterwards. (This is how I do upgrades >> with rpms.) If upgrading *does* restart the services, then you'd have >> to stop and disable them first (stop slurmctld, then slurmdbd), and >> after the upgrade, enable and start them (slurmdbd first), as others >> have answered. > > Readers must understand that we are discussing *minor release* upgrades only. True. I sorta forgot that a moment. :) Then you can upgrade and restart the two daemons in whichever order you want. > The slurmctld can be restarted immediately after upgrading without > slurmdbd being available, and thereby your cluster will keep running > without any interruption of service. A little later you can enable > and start slurmdbd, and the delay of slurmdbd doesn't cause any > problems for slurmctld or the users. I emphasize that we're > discussing *minor release* upgrades only! > > @Bjørn-Helge: Do you think there is good reason to start slurmdbd > before slurmctld when doing minor release upgrades? Not any more, it appears. But (unless my memory fails me again) earlier, slurmctld would refuse to start unless slurmdbd was running (when it was configured to use slurmdbd). Slurmctld would be fine with slurmdbd stopping while slurmctld was running, but upon start, it would require slurmdbd to be already running. -- Regards, Bjørn-Helge
signature.asc
Description: PGP signature
-- slurm-users mailing list -- slurm-users@lists.schedmd.com To unsubscribe send an email to slurm-users-le...@lists.schedmd.com
