Re: [slurm-users] QoS settings in sacctmgr requires restarting slurmctld to take effect

2019-01-11 Thread Jianwen Wei
Thank you. I sync /etc/slurm.conf from slurmctld node then then re-run slurmdbd as root, which seems to solve the problem. Before that, "sacctmgr list clusters" complained missing /etc/slurm.conf . Best, Jianwen > On Jan 11, 2019, at 12:33, Chris Samuel wrote: > > On 10/1/19 6:15 pm,

Re: [slurm-users] QoS settings in sacctmgr requires restarting slurmctld to take effect

2019-01-10 Thread Chris Samuel
On 10/1/19 6:15 pm, Jianwen Wei wrote: I am using SLURM 17.11 on CentOS 7. I find that QoS settings, say GrpNodes for an account, in sacctmgr requires restarting slurmcltd to take effect. This sounds like a configuration issue, and usually it's because slurmdbd cannot connect back to the con

[slurm-users] QoS settings in sacctmgr requires restarting slurmctld to take effect

2019-01-10 Thread Jianwen Wei
Hi, I am using SLURM 17.11 on CentOS 7. I find that QoS settings, say GrpNodes for an account, in sacctmgr requires restarting slurmcltd to take effect. Restarting slurmctld may hang slurm service for 15secs~60secs, which is annoying if QoS settings are configured several times a day dy