As discussed in this comment https://aur.archlinux.org/packages/slurm-llnl/#comment-795099 by Jakub Klinkovský in the Arch Linux User Repository the slurmctld systemd service does fully apply the new configuration on reload. The `ExecReload` line in the service file reads `ExecReload=/bin/kill -HUP $MAINPID` which should instruct slurmctld to reload its configuration. However, configuration changes like increasing or decreasing the time limit of a partition are not applied after a reload. Jakub Klinkovský, the original reporter of this issue, suggested to change the reload command to `ExecReload=/usr/bin/scontrol reconfigure`.
(In reply to Gordian Edenhofer from comment #0) > As discussed in this comment > https://aur.archlinux.org/packages/slurm-llnl/#comment-795099 by Jakub > Klinkovský in the Arch Linux User Repository the slurmctld systemd service > does fully apply the new configuration on reload. The `ExecReload` line in > the service file reads `ExecReload=/bin/kill -HUP $MAINPID` which should > instruct slurmctld to reload its configuration. However, configuration > changes like increasing or decreasing the time limit of a partition are not > applied after a reload. Jakub Klinkovský, the original reporter of this > issue, suggested to change the reload command to > `ExecReload=/usr/bin/scontrol reconfigure`. Thank you for the report, but I would not recommend that change. (a) 'scontrol reconfigure' issues a reconfiguration request to the entire cluster, which is likely not intended, and (b) it will not actually permit changes to certain other settings at this time. This is a limitation we're aware of and may address in the future, but in the meantime SIGHUP is the closest conceptually to what systemd is trying to do there.
Makes sense. Thanks for the explanation!