| Summary: | Preempt on both partition and QOS? | ||
|---|---|---|---|
| Product: | Slurm | Reporter: | Kilian Cavalotti <kilian> |
| Component: | Scheduling | Assignee: | Brian Christiansen <brian> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | 5 - Enhancement | ||
| Priority: | --- | CC: | brian, da |
| Version: | 14.11.8 | ||
| Hardware: | Linux | ||
| OS: | Linux | ||
| Site: | Stanford | Slinky Site: | --- |
| Alineos Sites: | --- | Atos/Eviden Sites: | --- |
| Confidential Site: | --- | Coreweave sites: | --- |
| Cray Sites: | --- | DS9 clusters: | --- |
| Google sites: | --- | HPCnow Sites: | --- |
| HPE Sites: | --- | IBM Sites: | --- |
| NOAA SIte: | --- | NoveTech Sites: | --- |
| Nvidia HWinf-CS Sites: | --- | OCF Sites: | --- |
| Recursion Pharma Sites: | --- | SFW Sites: | --- |
| SNIC sites: | --- | Tzag Elita Sites: | --- |
| Linux Distro: | --- | Machine Name: | |
| CLE Version: | Version Fixed: | 15.08.0 | |
| Target Release: | --- | DevPrio: | --- |
| Emory-Cloud Sites: | --- | ||
|
Description
Kilian Cavalotti
2015-07-08 10:39:29 MDT
You can preempt jobs based upon either QOS or partition, but not both. It would probably be messy, but you could possibly define a distinct QOS for each partition (e.g. high_batch, medium_batch, low_batch, high_interactive, medium_interactive, low_interactive, etc.). Hi Moe, Thanks for the confirmation. I guess we'll end up doing something like that in version 15.08, with the new QOS-to-partition binding. Cheers, -- Kilian Information about per-partition QOS here: http://slurm.schedmd.com/SLUG15/Partition_QOS.pdf Please re-open the ticket if this does not satisfy your needs and I can look at preempting jobs based upon either QOS or partition (both within the same cluster). That could be done, but requires a fair bit of code change. |