Next: condor_reconfig
Up: 5. Command Reference Manual
Previous: condor_prio
Subsections
condor_q
Display information about jobs in queue
condor_q
[-help]
[-global]
[-submitter submitter]
[-name name]
[-pool hostname]
[-analyze]
[-run]
[-long]
[{cluster | cluster.process | owner |
-constraint expression ... } ]
condor_q displays information about jobs in the Condor job queue. By
default, condor_q queries the local job queue but this behavior may be
modified by specifying:
- the -global option, which queries all job queues in the pool
- a schedd name with the -name option, which causes the queue of
the named schedd to be queried
- a submitter with the -submitter option, which causes all queues
of the named submitter to be queried
To restrict the display to jobs of interest, a list of zero or more
restrictions may be supplied. Each restriction may be one of:
- a cluster and a process matches jobs which
belong to the specified cluster and have the specified process number
- a cluster without a process matches all jobs belonging
to the specified cluster
- a owner matches all jobs owned by the specified owner
- a -constraint expression which matches all jobs that
satisfy the specified ClassAd expression. (See section 4.1
for a discussion of ClassAd expressions.)
If no owner restrictions are present in the list, the job matches the
restriction list if it matches at least one restriction in the list. If
owner restrictions are present, the job matches the list if it matches
one of the owner restrictions and at least one non-owner
restriction.
If the -long option is specified, condor_q displays a long description
of the jobs in the queue. Otherwise, a one line summary of information is
displayed as follows:
- ID
- The cluster/process id of the condor job.
- OWNER
- The owner of the job.
- SUBMITTED
- The month, day, hour, and minute the job was submitted to the
queue.
- CPU_USAGE
- Remote CPU time accumulated by the job to date in days,
hours, minutes, and seconds. (If the job is currently running, time
accumulated during the current run is not shown.)
- ST
- Current status of the job. U = unexpanded (never been run), H = on hold,
R = running, I = idle (waiting for a machine to execute on), C = completed,
and X = removed.
- PRI
- User specified priority of the job, ranges from -20 to +20, with
higher numbers corresponding to greater priority.
- SIZE
- The virtual image size of the executable in megabytes.
- CMD
- The name of the executable.
The -analyze option may be used to determine why certain jobs are not
running by performing an analysis on a per machine basis for each machine in
the pool. The reasons may vary among failed constraints, insufficient priority,
resource owner preferences and prevention of preemption by the
PREEMPTION_HOLD expression. If the -long option is specified
along with the -analyze option, the reason for failure is displayed on a
per machine basis.
Supported options are as follows:
- -help
- Get a brief description of the supported options
- -global
- Get queues of all the submitters in the system
- -submitter submitter
- List jobs of specific submitter
from all the queues in the pool
- -pool hostname
- Use hostname as the central manager to
locate schedds. (The default is the COLLECTOR_HOST specified
in the configuration file.
- -analyze
- Perform an approximate analysis to determine how
many resources are available to run the requested jobs
- -run
- Get information about running jobs.
- -name name
- Show only the job queue of the named schedd
- -long
- Display job ads in long format
- Restriction list
- The restriction list may have zero or more items,
each of which may be:
- cluster
- match all jobs belonging to cluster
- cluster.proc
- match all jobs belonging to cluster with
a process number of proc
- -constraint expression
- match all jobs which match
the ClassAd expression constraint
A job matches the restriction list if it matches any restriction in the
list Additionally, if owner restrictions are supplied, the job
matches the list only if it also matches an owner restriction.
Although -analyze provides a very good first approximation, the analyzer
cannot diagnose all possible situations because the analysis is based on
instantaneous and local information. Therefore, there are some situations
(such as when several submitters are contending for resources, or if the pool
is rapidly changing state) which cannot be accurately diagnosed.
Condor Team, University of Wisconsin-Madison
Copyright © 1990-1998 Condor Team, Computer Sciences Department,
University of Wisconsin-Madison, Madison, WI. All Rights Reserved.
No use of the Condor Software Program is authorized
without the express consent of the Condor Team. For more information
contact: Condor Team, Attention: Professor Miron Livny,
7367 Computer Sciences, 1210 W. Dayton St., Madison, WI 53706-1685,
(608) 262-0856 or miron@cs.wisc.edu.
U.S. Government Rights Restrictions: Use, duplication, or disclosure
by the U.S. Government is subject to restrictions as set forth in
subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer
Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and
(2) of Commercial Computer Software-Restricted Rights at 48 CFR
52.227-19, as applicable, Condor Team, Attention: Professor Miron
Livny, 7367 Computer Sciences, 1210 W. Dayton St., Madison,
WI 53706-1685, (608) 262-0856 or miron@cs.wisc.edu.
See the Condor Version 6.1.2 Manual for
additional notices.
Next: condor_reconfig
Up: 5. Command Reference Manual
Previous: condor_prio
condor-admin@cs.wisc.edu