Ticket 2773

Summary: Jobs sitting in the queue not running due to priority
Product: Slurm Reporter: Hadrian <hxd58>
Component: SchedulingAssignee: Tim Wickberg <tim>
Status: RESOLVED INFOGIVEN QA Contact:
Severity: 3 - Medium Impact    
Priority: ---    
Version: 14.11.5   
Hardware: Linux   
OS: Linux   
Site: Case 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:
Target Release: --- DevPrio: ---
Emory-Cloud Sites: ---
Attachments: slurm.conf

Description Hadrian 2016-05-26 04:44:51 MDT 
Created attachment 3151 [details]
slurm.conf

We have a job sitting in the queue due to Priority although the priority number does not seem to be that low. 

Is there a way to force that particular job to run despite of the priority number ?

Thanks,
Hadrian
Comment 1 Tim Wickberg 2016-05-26 04:54:19 MDT 
Priority numbers only matter in respect to the priority of other jobs, there's no specific threshold for a value to "matter".

If you want to force-set the priority value, you can do manually set it (as an admin) with 'scontrol update jobid=12345 priority=100000'.
Comment 2 Tim Wickberg 2016-05-31 04:58:05 MDT 
Marking this as resolved/infogiven. Please reopen if I can answer anything else on this.

- Tim