Danny Auble <[email protected]> writes:
> This would be very safe to do. You can most likely update to 2.3.3 with > no problems as well. Running jobs should continue merrily along in > either case. Only bug fixes have been done from 2.2.4 to 2.2.7 so in > this case you shouldn't need to wait for a drained node to update but if > you feel safer doing that a 2.2.4 slurmd will work just fine with a > 2.2.7 slurmctld. I think we may have a slight problem with our StateSaveLocation due to the way SLURM has been packaged and set up by the vendor of our cluster management software. Currently we have StateSaveLocation=/nfs/share/apps/slurm/2.2.4/statesave The new version of SLURM will be installed to /nfs/share/apps/slurm/2.2.7 My understanding is that we would, at least initially, have to keep the StateSaveLocation as is with the 2.2.4-path. It would be desirable, however, for the StateSaveLocation to be independent of the SLURM version, say /nfs/share/apps/slurm/statesave What precautions would be needed before making such a change? Would it just be a question of stopping the slurmctld, moving the contents of the current statesave directory, changing the configuration in slurm.conf, and then restarting slurmctld? Would the slurmds be affected? Cheers Loris -- Dr. Loris Bennett (Mr.) ZEDAT, Freie Universität Berlin Email [email protected]
