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

Brian Andrus toomuchit at gmail.com
Wed Feb 2 23:49:32 UTC 2022

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. You will still need to do the incremental for the db 
changes, but no worries about state files either way.

Brian Andrus

On 2/2/2022 1:38 PM, Nathan Smith wrote:
> 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 versions will not be recognized and will be
>> discarded, resulting in loss of all running and pending jobs.
> We are planning for an upgrade from 17.02.11 to 21.08.2. As a part of
> our upgrade procedure we'd be bringing the scheduler to full stop, so
> the loss of running and pending jobs would not be a concern. Is there
> anything more to state information than running and pending jobs? For
> example, would the JobID count revert to 1 in the case of such an
> upgrade?
> [0] https://slurm.schedmd.com/quickstart_admin.html#upgrade

More information about the slurm-users mailing list