[slurm-users] Interlocking / Concurrent runner

Florian Lohoff f at zz.de
Tue Oct 22 09:55:41 UTC 2019

On Tue, Oct 22, 2019 at 12:06:57PM +0300, mercan wrote:
> Hi;
> You can use the "--dependency=afterok:jobid:jobid ..." parameter of the
> sbatch to ensure the new submitted job will be waiting until all older jobs
> are finished. Simply, you can submit the new job even while older jobs are
> running, the new job will not start before old jobs are finished.

I am using than - But imaging a job collection of 20-40 Jobs. Running
taking 2 1/2 hours. Then i'd like to run the same jobs again.

So i would need to record all jobids of the last batch run 
to start the next.

Florian Lohoff                                                 f at zz.de
        UTF-8 Test: The 🐈 ran after a 🐁, but the 🐁 ran away
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20191022/1ecc7ab4/attachment.sig>

More information about the slurm-users mailing list