You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now we have qdel <job ID> which enables us to terminate a specified job, and qdel all to kill all jobs.
But when we have several job batchs running, each of which has a big number of jobs (say 100 for each job batch), it becomes inconvenient to kill all jobs in a specified job batch.
What we can do is to write a script somewhere in the repo that extracts all job IDs belonging to a specified job batch, and feed those job IDs into qdel. And when we use it, we just need to type something like
smart_dispatch --killjobbatch <job batch id>
The text was updated successfully, but these errors were encountered:
Thank you for letting us know about useful features smart-dispatch should have.
Right now, the job IDs are stored in SMART_DISPATCH_LOGS/{job_name}/job_ids.txt, so it should not be to hard to write a script that parses the file and call qdel on each.
Now we have
qdel <job ID>
which enables us to terminate a specified job, andqdel all
to kill all jobs.But when we have several job batchs running, each of which has a big number of jobs (say 100 for each job batch), it becomes inconvenient to kill all jobs in a specified job batch.
What we can do is to write a script somewhere in the repo that extracts all job IDs belonging to a specified job batch, and feed those job IDs into
qdel
. And when we use it, we just need to type something likeThe text was updated successfully, but these errors were encountered: