On 09-08-2022 01:11, David Magda wrote:
On Aug 6, 2022, at 15:13, Chris Samuel wrote:
It's also safe to restart slurmd's with running jobs, though you may want to
drain them before that so slurmctld won't try and send them a job in the middle.
My testing has shown that this is not the case:
On Aug 6, 2022, at 15:13, Chris Samuel wrote:
>
> On 6/8/22 10:43 am, David Magda wrote:
>
>> It seems that the the new srun(1) cannot talk to the old slurmd(8).
>> Is this 'on purpose'? Does the backwards compatibility of the protocol not
>> extend to srun(1)?
>
> That's expected, what you're
On 6/8/22 10:43 am, David Magda wrote:
It seems that the the new srun(1) cannot talk to the old slurmd(8).
Is this 'on purpose'? Does the backwards compatibility of the protocol not
extend to srun(1)?
That's expected, what you're hoping for here is forward compatibility.
Newer daemons know
Hello,
We are testing the upgrade process with going from 20.11.9 to 22.05.2. The
master server is running 22.05.2 slurmctld/slurmdbd, and the compute nodes are
(currently) running slurm-20.11.9 slurmd. We are running this 'mixed
environment' because our production cluster has a reasonable numb
