| Summary: | preemption: possible to allow a reservation to preempt jobs? | ||
|---|---|---|---|
| Product: | Slurm | Reporter: | Doug Jacobsen <dmjacobsen> |
| Component: | slurmctld | Assignee: | Tim Wickberg <tim> |
| Status: | RESOLVED INFOGIVEN | QA Contact: | |
| Severity: | 4 - Minor Issue | ||
| Priority: | --- | ||
| Version: | 15.08.8 | ||
| Hardware: | Linux | ||
| OS: | Linux | ||
| Site: | NERSC | 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
Doug Jacobsen
2016-03-28 02:42:38 MDT
When you say "preempted" here, you mean canceled at that time presumably? Suspend + resume, or gang scheduling obviously wouldn't work if you're bringing the machine down. Could the jobs simply be submitted with a modest --time-min set? sched/backfill would then try to assign them as much time is available that schedules them soonest, which seems like what you're trying to accomplish to a limited extent. You may want to combine that (possibly through a job_submit plugin) with a dedicated lower-priority partition to limit churn. I think this is a great solution -- I'll work with our user services folks to get users to do this! Thanks, Doug |