Ticket 6594

Summary: Improve pending hetjobs state_reason
Product: Slurm Reporter: Alejandro Sanchez <alex>
Component: SchedulingAssignee: Alejandro Sanchez <alex>
Status: RESOLVED FIXED QA Contact:
Severity: 4 - Minor Issue    
Priority: --- CC: c.paschoulas, d.krause
Version: 18.08.5   
Hardware: Linux   
OS: Linux   
See Also: https://bugs.schedmd.com/show_bug.cgi?id=5579
Site: Jülich 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: 18.08.7 19.05.0pre4
Target Release: --- DevPrio: ---
Emory-Cloud Sites: ---

Description Alejandro Sanchez 2019-02-26 11:24:50 MST 
Coming from bug 5579 to decouple this issue in a separate bug.

1. We can document that hetjobs won't change their PD state_reason until evaluated by backfill. So it will remain (None) until evaluated. We discussed internally and we don't like the idea of adding a hetjob creation time waiting reason of WAIT_BACKFILL or something, WAIT_NO_REASON (None) till evaluated by backfill seems ok to us.

2. Once evaluated by backfill, set an initial state_reason of WAIT_RESOURCES and let backfill change it accordingly if needed. WAIT_PRIORITY doesn't make much sense in backfill since its a concept more tied to the main scheduler when a job in a partition fails to be allocated and rest of jobs in the partition then are set to WAIT_PRIORITY.
Comment 6 Alejandro Sanchez 2019-03-22 04:51:17 MDT 
Hi,

this has been fixed in the following commit available since 18.08.7:

https://github.com/SchedMD/slurm/commit/695456d48ed7ff0ad