Hey Mike -
Please feel free to open questions of this nature in our Bugzilla instance; that's our preferred method for answering customer requests. Additional responses are inline below - I mainly want to highlight that this is not a trivial change, and will need some planning and research on your end to change successfully.
We would like to change the name of our cluster to something more site specific via editing slurm.conf variable ClusterName. After making the change, would we only need to restart slurmctld on the master, or would it require restarting the slurmd services on all compute nodes and slurmctld and slurmdbd on the master? i.e. a full cluster restart ... do this during a scheduled maintenance window?
You'd need to restart everything, override one sanity check file kept in StateSaveLocation, and add the new cluster name through sacctmgr.
Are there any gotchas that we'd need to look out for after changing the name? For example, is this going to affect anything in the MySQL database and sacct lookups?
Yes, several. Any associations and limits you've put in place for the original cluster name would not carry over; you'd need to rebuild them.
'sacct -M old_name' would let you access the historical usage records from the previous cluster name.
If you have further questions please file the issue in Bugzilla, and we'd be happy to help address this.
- Tim -- Tim Wickberg Director of Support, SchedMD, LLC Commercial Slurm Development and Support
