Thanks Paul! Would you know the answer to:
Question 2: Can anyone confirm that the output "slurmdbd: debug2:
Everything rolled up" indeed signifies that conversion is complete?
Thanks,
Ole
On 06/26/2017 04:02 PM, Paul Edmon wrote:
Yeah, we keep around a test cluster environment for that p
Yeah, we keep around a test cluster environment for that purpose to vet
slurm upgrades before we roll them on the production cluster.
Thus far no problems. However, paranoia is usually a good thing for
cases like this.
-Paul Edmon-
On 06/26/2017 07:30 AM, Ole Holm Nielsen wrote:
On 06/
On 06/26/2017 01:24 PM, Loris Bennett wrote:
We have also upgraded in place continuously from 2.2.4 to currently
16.05.10 without any problems. As I mentioned previously, it can be
handy to make a copy of the statesave directory, once the daemons have
been stopped.
However, if you want to know
Hi Ole,
We have also upgraded in place continuously from 2.2.4 to currently
16.05.10 without any problems. As I mentioned previously, it can be
handy to make a copy of the statesave directory, once the daemons have
been stopped.
However, if you want to know how long the upgrade might take, then
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 powe
