[slurm-users] Slurm node weights

[Sarlo, Jeffrey S]

Which version of Slurm are you running?  I know some of the earlier versions of 18.08 had a bug and node weights were not working.


Jeff


________________________________
From: slurm-users <slurm-users-bounces at lists.schedmd.com> on behalf of David Baker <D.J.Baker at soton.ac.uk>
Sent: Thursday, July 25, 2019 6:09 AM
To: slurm-users at lists.schedmd.com <slurm-users at lists.schedmd.com>
Subject: Re: [slurm-users] Slurm node weights


Hello,


As an update I note that I have tried restarting the slurmctld, however that doesn't help.


Best regards,

David

________________________________
From: slurm-users <slurm-users-bounces at lists.schedmd.com> on behalf of David Baker <D.J.Baker at soton.ac.uk>
Sent: 25 July 2019 11:47:35
To: slurm-users at lists.schedmd.com <slurm-users at lists.schedmd.com>
Subject: [slurm-users] Slurm node weights


Hello,


I'm experimenting with node weights and I'm very puzzled by what I see. Looking at the documentation I gathered that jobs will be allocated to the nodes with the lowest weight which satisfies their requirements. I have 3 nodes in a partition and I have defined the nodes like so..


NodeName=orange01 Procs=48 Sockets=8 CoresPerSocket=6 ThreadsPerCore=1 RealMemory=1018990 State=UNKNOWN Weight=50
NodeName=orange[02-03] Procs=48 Sockets=8 CoresPerSocket=6 ThreadsPerCore=1 RealMemory=1018990 State=UNKNOWN


So, given that the default weight is 1 I would expect jobs to be allocated to orange02 and orange03 first. I find, however that my test job is always allocated to orange01 with the higher weight. Have I overlooked something? I would appreciate your advice, please.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20190725/d12f56d1/attachment.htm>