t kill all jobs due to timeouts. Better to
be safe than sorry.
I don't expect to inform the users, since the operation is expected to
run smoothly without troubles for user jobs.
Thanks,
Ole
Re: [slurm-dev] Dry run upgrade procedure for the slurmdbd database
Question 2: Can anyo
the slurmdbd will be down
so that the cluster doesn't kill all jobs due to timeouts. Better to
be safe than sorry.
I don't expect to inform the users, since the operation is expected to
run smoothly without troubles for user jobs.
Thanks,
Ole
Re: [slurm-dev] Dry run upgrade procedure
long the slurmdbd will be down so
that the cluster doesn't kill all jobs due to timeouts. Better to be
safe than sorry.
I don't expect to inform the users, since the operation is expected to
run smoothly without troubles for user jobs.
Thanks,
Ole
Re: [slurm-dev] Dry run upgrade procedure
, then yours
is a good approach. What is your use case here? Do you want to inform
the users about the length of the outage with regard to job submission?
Cheers,
Loris
Lachlan Musicman <data...@gmail.com> writes:
> Re: [slurm-dev] Dry run upgrade procedure for the slurmdbd database
&
We did it in place, worked as noted on the tin. It was less painful than I
expected. TBH, your procedures are admirable, but you shouldn't worry -
it's a relatively smooth process.
cheers
L.
--
"Mission Statement: To provide hope and inspiration for collective action,
to build collective
