Ticket 5459

Summary:	specifying job dependency on already terminated job
Product:	Slurm	Reporter:	George Hwa <george.hwa>
Component:	User Commands	Assignee:	Director of Support <support>
Status:	RESOLVED INFOGIVEN	QA Contact:
Severity:	3 - Medium Impact
Priority:	---	CC:	alex
Version:	17.02.7
Hardware:	Linux
OS:	Linux
Site:	KLA-Tencor RAPID	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 George Hwa 2018-07-20 17:12:36 MDT

When sbatch submitting a new job, if the dependent job has already terminated abnormally (FAILED), will the new job run at all?

Comment 1 Alejandro Sanchez 2018-07-23 02:55:18 MDT

Yes, unless you specify a dependency type[1] that would never be satisfied. For instance:

 afterok:job_id[:jobid...]
This job can begin execution after the specified jobs have successfully executed (ran to completion with an exit code of zero).

This would never be satisfied because the specified job didn't exit with 0 code. But if you specify after, or afterany or afternotok the job should run.

You might also be interested in the SchedulerParameters option kill_invalid_depend:

 kill_invalid_depend
If a job has an invalid dependency and it can never run terminate it and set its state to be JOB_CANCELLED. By default the job stays pending with reason DependencyNeverSatisfied.

[1] https://slurm.schedmd.com/sbatch.html#OPT_dependency