Re: [slurm-users] Upgrade from 17.02.11 to 21.08.2 and state information

2022-02-04 Thread Ole Holm Nielsen
On 03-02-2022 21:59, Ryan Novosielski wrote: On Feb 3, 2022, at 2:55 PM, Ole Holm Nielsen wrote: On 03-02-2022 16:37, Nathan Smith wrote: Yes, we are running slurmdbd. We could arrange enough downtime to do an incremental upgrade of major versions as Brian Andrus suggested, at least on the s

Re: [slurm-users] Upgrade from 17.02.11 to 21.08.2 and state information

2022-02-04 Thread Ole Holm Nielsen
On 04-02-2022 08:59, Bjørn-Helge Mevik wrote: Ole Holm Nielsen writes: As Brian Andrus said, you must upgrade Slurm by at most 2 major versions, and that includes slurmd's as well! Don't do a "direct upgrade" of slurmd by more than 2 versions! That should only be an issue if you have runnin

Re: [slurm-users] Upgrade from 17.02.11 to 21.08.2 and state information

2022-02-04 Thread Bjørn-Helge Mevik
Ole Holm Nielsen writes: > As Brian Andrus said, you must upgrade Slurm by at most 2 major > versions, and that includes slurmd's as well! Don't do a "direct > upgrade" of slurmd by more than 2 versions! That should only be an issue if you have running jobs during the upgrade, shouldn't it? A

Re: [slurm-users] Upgrade from 17.02.11 to 21.08.2 and state information

2022-02-03 Thread Ryan Novosielski
> On Feb 3, 2022, at 2:55 PM, Ole Holm Nielsen > wrote: > > On 03-02-2022 16:37, Nathan Smith wrote: >> Yes, we are running slurmdbd. We could arrange enough downtime to do an >> incremental upgrade of major versions as Brian Andrus suggested, at least on >> the slurmctld and slurmdbd system

Re: [slurm-users] Upgrade from 17.02.11 to 21.08.2 and state information

2022-02-03 Thread Ole Holm Nielsen
m-users *On Behalf Of *Brian Haymore *Sent:* Wednesday, February 2, 2022 1:51 PM *To:* slurm-us...@schedmd.com; Slurm User Community List *Subject:* [EXTERNAL] Re: [slurm-users] Upgrade from 17.02.11 to 21.08.2 and state information Are you running slurmdbd in your current setup?  If you ar

Re: [slurm-users] Upgrade from 17.02.11 to 21.08.2 and state information

2022-02-03 Thread Nathan Smith
.com>> on behalf of Nathan Smith mailto:smina...@ohsu.edu>> Sent: Wednesday, February 2, 2022 2:38 PM To: slurm-us...@schedmd.com<mailto:slurm-us...@schedmd.com> mailto:slurm-us...@schedmd.com>> Subject: [slurm-users] Upgrade from 17.02.11 to 21.08.2 and state information T

Re: [slurm-users] Upgrade from 17.02.11 to 21.08.2 and state information

2022-02-02 Thread Brian Andrus
I actually just did that path for a children's hospital. It was fairly straight-forward. Running jobs were not affected. You do need to go 17->18->19->20->21 This is because there were changes in the db schema. If you plan on bringing everything to a stop (no running jobs), you should be good

Re: [slurm-users] Upgrade from 17.02.11 to 21.08.2 and state information

2022-02-02 Thread Brian Haymore
-558-1150, Fax: 801-585-5366 http://bit.ly/1HO1N2C From: slurm-users on behalf of Nathan Smith Sent: Wednesday, February 2, 2022 2:38 PM To: slurm-us...@schedmd.com Subject: [slurm-users] Upgrade from 17.02.11 to 21.08.2 and state information The "Upg

[slurm-users] Upgrade from 17.02.11 to 21.08.2 and state information

2022-02-02 Thread Nathan Smith
The "Upgrades" section of the quick-start guide [0] warns: > Slurm permits upgrades to a new major release from the past two major > releases, which happen every nine months (e.g. 20.02.x or 20.11.x to > 21.08.x) without loss of jobs or other state information. State > information from older ver