Remove jobs from the queue
Remove Jobs From the Queue[edit | edit source]
The goal of this exercise is to show you how to remove jobs from the queue. This is helpful if you make a mistake, do not want to wait for a job to complete, or otherwise need to fix things. For example, if some test jobs go on hold for using too much memory or disk, you may want to just remove them, edit the submit files, and then submit again.
NOTE: Please remember to remove any jobs from the queue that you have given up on. Otherwise, the queue will start to get very long with jobs that will waste resources (and decrease your priority!), or that may never run (if they're on hold, or have other issues keeping them from matching).
This exercise is very short, but if you are out of time, you can come back to it later.
Removing a Job From the Queue [edit | edit source]
To practice removing jobs from the queue, you need a job in the queue!
- Submit a job from an earlier exercise
- Determine the job ID (
cluster.process) from the
condor_submitoutput or from
- Remove the job:Use the full job ID this time, e.g.,
$ condor_rm <job id>
- Did the job leave the queue immediately? If not, about how long did it take?
.0part of the job ID). That will change soon, so it is good to know how to remove a specific job ID. However, it is possible to remove all jobs that are part of a cluster at once. Simply omit the job process (the
.0part of the job ID) in the
$ condor_rm <cluster>
condor_rmcommand. For example:
$ condor_rm 5768 5769 5770.0 5771.2
Removing All of Your Jobs [edit | edit source]
If you really want to remove all of your jobs at once, you can do that.
- Quickly submit several jobs from past exercises
- View the jobs in the queue with
- Remove them all at once
$ condor_rm <username>
condor_qto track progress
In case you are wondering, you can remove only your own jobs. HTCondor administrators can remove anyone’s jobs, so be nice to them.