Hi Loris, "Loris Bennett" <[email protected]> writes:
>> Actually, in my case, I don't need to preserve state information, as no >> jobs will be running at the time of the upgrade but I am using >> SlurmDBD. Specifically I want to upgrade from version 2.4.5 to 14.11. >> From the documentation I would assume that this upgrade can be done in a >> single step. Is this correct? Remember that the state files also include all queued jobs, the current job id, node states and so on. > Any thoughts on this? Can I go directly from 2.4.5 to 14.11 and > preserve the information in SlurmDBD if no jobs are running? Our > maintenance downtime starts on Monday, so it would be helpful to know by > then. I recommend testing the upgrade in a development environment first. If you use the same hostnames you can copy the database and state files from the production system to the dev system then do a test upgrade. Unless some of the developers state that a direct upgrade is supported I would assume that it isn't. I would do something like this: * Stop all slurmds * Stop slurmctld * Stop slurmdbd * Upgrade packages to latest 2.6.x * Start slurmdbd - This will upgrade the database tables to 2.6 level - Monitor slurmdbd.log and wait until it is done * Start slurmctld - This will upgrade state files to 2.6 level - Monitor slurmctld.log and wait until it is done * Repeat the process for 14.11 Our largest cluster is also still running 2.4.5 so I will also need to do this eventually, so please let us know if you run into any issues. If you use JobSubmitPlugins=lua you need to update your script as the interface changes in 14.11. Regards, Pär Lindfors
