| Summary: | Discrepancy between partition requested by a job and node allocated to the job | ||
|---|---|---|---|
| Product: | Slurm | Reporter: | HPC Admin <hpcadmin> |
| Component: | Scheduling | Assignee: | Tim McMullan <mcmullan> |
| Status: | RESOLVED INFOGIVEN | QA Contact: | |
| Severity: | 3 - Medium Impact | ||
| Priority: | --- | ||
| Version: | 20.02.5 | ||
| Hardware: | Linux | ||
| OS: | Linux | ||
| Site: | Auburn | 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: | --- |
|
Description
HPC Admin
2021-04-13 08:27:08 MDT
Hi Keenan, AllocNode represents the node that requested the allocation, not a node that has been allocated. From that output, it appears that the job was submitted from node502, and hasn't yet been scheduled due to a maintenance reservation. How long after it was submitted was "scontrol show job" run? Depending on your configuration something like "SchedNodeList=some_nodes" may appear. This would tell you where that job is expected to actually run when the nodes become available again. Thanks! --Tim OK. That makes sense. How do we restrict users to the login node for job submission? Keenan You should be able to limit what nodes you can submit from by setting "AllocNodes=" with all of your login nodes. It is a partition specific option, so you would need to set it for every partition you wanted to limit. Thanks! --Tim Thank you for the help. You can close this ticket. Keenan Sure thing! Closing this now. |