remove jobs from the HTCondor queue
condor_rm [-help | -version ]
condor_rm [-debug ] [-forcex ] [ -pool centralmanagerhostname[:portnumber] | -name scheddname ] | [-addr “<a.b.c.d:port>”] cluster… | cluster.process… | user… | -constraint expression …
condor_rm [-debug ] [ -pool centralmanagerhostname[:portnumber] | -name scheddname ] | [-addr “<a.b.c.d:port>”] -all
condor_rm removes one or more jobs from the HTCondor job queue. If
the -name option is specified, the named condor_schedd is
targeted for processing. Otherwise, the local condor_schedd is
targeted. The jobs to be removed are identified by one or more job
identifiers, as described below. For any given job, only the owner of
the job or one of the queue super users (defined by the
QUEUE_SUPER_USERS macro) can remove the job.
When removing a grid job, the job may remain in the “X” state for a very long time. This is normal, as HTCondor is attempting to communicate with the remote scheduling system, ensuring that the job has been properly cleaned up. If it takes too long, or in rare circumstances is never removed, the job may be forced to leave the job queue by using the -forcex option. This forcibly removes jobs that are in the “X” state without attempting to finish any clean up at the remote scheduler.
Display usage information
Display version information
- -pool centralmanagerhostname[:portnumber]
Specify a pool by giving the central manager’s host name and an optional port number
- -name scheddname
Send the command to a machine identified by scheddname
- -addr “<a.b.c.d:port>”
Send the command to a machine located at “<a.b.c.d:port>”
Causes debugging information to be sent to
stderr, based on the value of the configuration variable
Force the immediate local removal of jobs in the ‘X’ state (only affects jobs already being removed)
Remove all jobs in the specified cluster
Remove the specific job in the cluster
Remove jobs belonging to specified user
- -constraint expression
Remove all jobs which match the job ClassAd expression constraint
Remove all the jobs in the queue
Use the -forcex argument with caution, as it will remove jobs from the local queue immediately, but can orphan parts of the job that are running remotely and have not yet been stopped or removed.
For a user to remove all their jobs that are not currently running:
$ condor_rm -constraint 'JobStatus =!= 2'
condor_rm will exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.