Summary: | CPUs=1 match no Sockets, Sockets*CoresPerSocket or Sockets*CoresPerSocket*ThreadsPerCore. Resetting CPUs. | ||
---|---|---|---|
Product: | Slurm | Reporter: | Ole.H.Nielsen <Ole.H.Nielsen> |
Component: | Configuration | Assignee: | Felip Moll <felip.moll> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | 3 - Medium Impact | ||
Priority: | --- | CC: | felip.moll |
Version: | 20.02.3 | ||
Hardware: | Linux | ||
OS: | Linux | ||
Site: | DTU Physics | Alineos Sites: | --- |
Atos/Eviden Sites: | --- | Confidential Site: | --- |
Coreweave sites: | --- | Cray Sites: | --- |
DS9 clusters: | --- | HPCnow Sites: | --- |
HPE Sites: | --- | IBM Sites: | --- |
NOAA SIte: | --- | OCF Sites: | --- |
Recursion Pharma Sites: | --- | SFW Sites: | --- |
SNIC sites: | --- | Linux Distro: | --- |
Machine Name: | CLE Version: | ||
Version Fixed: | Target Release: | --- | |
DevPrio: | --- | Emory-Cloud Sites: | --- |
Attachments: | slurm.conf |
Description
Ole.H.Nielsen@fysik.dtu.dk
2020-06-16 00:44:52 MDT
When I change slurm.conf lines: NodeName=a[001-140] Weight=10001 Boards=1 SocketsPerBoard=2 CoresPerSocket=4 ThreadsPerCore=1 ... into NodeName=a[001-140] Weight=10001 Sockets=2 CoresPerSocket=4 ThreadsPerCore=1 ... then the errors do not show up! It appears that Boards=1 SocketsPerBoard=2 is not supported correctly in 20.02.3, and that one must in stead use Sockets=2. Question: Should Boards and SocketsPerBoard be working correctly, or should these parameters be deprecated? Thanks, Ole Thanks Ole, as you have guessed this is a duplicate of 9233. I am investigating the regression right now. I am marking this but as duplicate, so please, follow the other one from now on. Thank you for your help. *** This bug has been marked as a duplicate of bug 9233 *** |