[slurm-users] Dependencies with singleton and after

Jarno van der Kolk jvanderk at uottawa.ca
Fri Aug 23 14:19:18 UTC 2019

Yeah, it's tricky. I suggested the afterany to the researcher as well, but it wasn't compatible with their workflow as some jobs are allowed to run simultaneously, but they can still have dependencies on each other. They are using groups of singletons which I left out of the minimal working example to get to the core of the issue.

I think Kevin Buckley's interpretation is indeed what happens in that a circular dependency was created.
However, I'm still puzzled if that is by design or a potential bug in SLURM.

Any thoughts on that?


Jarno van der Kolk, PhD Phys.
Analyste principal en informatique scientifique | Senior Scientific Computing Specialist
Solutions TI | IT Solutions
Université d’Ottawa | University of Ottawa

From: slurm-users <slurm-users-bounces at lists.schedmd.com> on behalf of Brian Andrus <toomuchit at gmail.com>
Sent: August 22, 2019 10:20 AM
To: slurm-users at lists.schedmd.com <slurm-users at lists.schedmd.com>
Subject: Re: [slurm-users] Dependencies with singleton and after

I've actually never used singleton and merely chained dependencies. Maybe you can do that as a workaround:

waitjob=$(sbatch --hold fakejob.sh |sed 's/Submitted batch job //')
for i in {1..2}; do
  echo Submitting $VAULT to run after ${waitjob}
  waitjob=$(sbatch -H --depend=afterany:${waitjob} fakejob.sh|sed 's/Submitted batch job //')

Of course, if you are actually running the exact same script, I would recommend using arrays as well.
Brian Andrus

More information about the slurm-users mailing list