Re: [slurm-users] Interlocking / Concurrent runner

2019-10-22 Thread Reuti
Hi, I'm more used to GridEngine but use SLURM at remote locations. What I miss in SLURM are two features which I think are related to this area: • use job names with wildcards for the various command like `scancel` • use job names with wildcards for --dependency If I get you right, you would l

Re: [slurm-users] Interlocking / Concurrent runner

2019-10-22 Thread Florian Lohoff
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 > run

Re: [slurm-users] Interlocking / Concurrent runner

2019-10-22 Thread mercan
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.

[slurm-users] Interlocking / Concurrent runner

2019-10-22 Thread Florian Lohoff
Hi, i am using slurm in a single node job batching system. Slurm ist perfect for that case and works for a couple years flawlessly. Lately i was shuffleing around jobs which take much longer to run to only run daily, and other jobs to run more frequently. A Question i had was - is there a possib