Hi Bjørn-Helge,
On 3/10/25 08:50, Bjørn-Helge Mevik via slurm-users wrote:
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 slurmdb
Ole Holm Nielsen via slurm-users 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 f
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
w
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
On 3/6/25 18:10, Paul Musset via slurm-users wrote:
If they are on two different machines, doing as described on the slurm
documentation is not a problem. I just updated an ubuntu installation a
few days ago following the doc and they can both can run without the other
running
If they are on
Hi,
If they are on two different machines, doing as described on the slurm
documentation is not a problem. I just updated an ubuntu installation a
few days ago following the doc and they can both can run without the
other running
If they are on the same machine, my guess would be that you ha
