condor_q(1) General Commands Manual condor_q(1)
Name
condor_q Display - information about jobs in queue
Synopsis
condor_q [-help]
condor_q[-debug] [-global] [-submitter submitter] [-name name] [-pool centralmanagerhostname[:portnumber]] [-analyze] [-run] [-hold]
[-globus] [-goodput] [-io] [-dag] [-long] [-xml] [-attributes Attr1 [,Attr2 ... ]] [-format fmt attr] [-cputime] [-currentrun] [-avgqueue-
time] [-jobads file] [-machineads file] [-stream-results] [-wide] [{cluster | cluster.process | owner | -constraint expression... } ]
Description
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 -globaloption, which queries all job queues in the pool
* a schedd name with the -nameoption, which causes the queue of the named schedd to be queried
* a submitter with the -submitteroption, 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 clusterand a processmatches jobs which belong to the specified cluster and have the specified process number
* a clusterwithout a processmatches all jobs belonging to the specified cluster
* a ownermatches all jobs owned by the specified owner
* a -constraint expressionwhich matches all jobs that satisfy the specified ClassAd expression. (See section 4.1for a discussion of
ClassAd expressions.) If no ownerrestrictions are present in the list, the job matches the restriction list if it matches at least one
restriction in the list. If ownerrestrictions are present, the job matches the list if it matches one of the ownerrestrictions andat
least one non-owner restriction.
If the -longoption is specified, condor_qdisplays a long description of the queried jobs by printing the entire job ClassAd. The attributes
of the job ClassAd may be displayed by means of the -formatoption, which displays attributes with a printf(3) format. Multiple -formatop-
tions may be specified in the option list to display several attributes of the job. If neither -longor -formatare specified, condor_qdis-
plays a a one line summary of information 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.
RUN_TIME
Wall-clock time accumulated by the job to date in days, hours, minutes, and seconds.
ST
Current status of the job, which varies somewhat according to the job universe and the timing of updates. H = on hold, R = running, I =
idle (waiting for a machine to execute on), C = completed, X = removed, and > = transferring output.
PRI
User specified priority of the job, ranges from -20 to +20, with higher numbers corresponding to greater priority.
SIZE
The value of job ClassAd attribute MemoryUsage (in Mbytes), when the attribute is defined, and ImageSize (in Kbytes), otherwise.
CMD
The name of the executable.
If the -dagoption is specified, the OWNER column is replaced with NODENAME for jobs started by the condor_dagmaninstance.
If the -runoption is specified, the ST, PRI, SIZE, and CMD columns are replaced with:
HOST(S)
The host where the job is running.
If the -globusoption is specified, the ST, PRI, SIZE, and CMD columns are replaced with:
STATUS
The state that Condor believes the job is in. Possible values are
PENDING
The job is waiting for resources to become available in order to run.
ACTIVE
The job has received resources, and the application is executing.
FAILED
The job terminated before completion because of an error, user-triggered cancel, or system-triggered cancel.
DONE
The job completed successfully.
SUSPENDED
The job has been suspended. Resources which were allocated for this job may have been released due to a scheduler-specific reason.
UNSUBMITTED
The job has not been submitted to the scheduler yet, pending the reception of the GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_COMMIT_REQUEST sig-
nal from a client.
STAGE_IN
The job manager is staging in files, in order to run the job.
STAGE_OUT
The job manager is staging out files generated by the job.
UNKNOWN
MANAGER
A guess at what remote batch system is running the job. It is a guess, because Condor looks at the Globus jobmanager contact string to
attempt identification. If the value is fork, the job is running on the remote host without a jobmanager. Values may also be condor,
lsf, or pbs.
HOST
The host to which the job was submitted.
EXECUTABLE
The job as specified as the executable in the submit description file.
If the -goodputoption is specified, the ST, PRI, SIZE, and CMD columns are replaced with:
GOODPUT
The percentage of RUN_TIME for this job which has been saved in a checkpoint. A low GOODPUT value indicates that the job is failing to
checkpoint. If a job has not yet attempted a checkpoint, this column contains [?????] .
CPU_UTIL
The ratio of CPU_TIME to RUN_TIME for checkpointed work. A low CPU_UTIL indicates that the job is not running efficiently, perhaps
because it is I/O bound or because the job requires more memory than available on the remote workstations. If the job has not (yet)
checkpointed, this column contains [??????] .
Mb/s
The network usage of this job, in Megabits per second of run-time.
If the -iooption is specified, the ST, PRI, SIZE, and CMD columns are replaced with:
READ The total number of bytes the application has read from files and sockets.
WRITE The total number of bytes the application has written to files and sockets.
SEEK The total number of seek operations the application has performed on files.
XPUT The effective throughput (average bytes read and written per second) from the application's point of view.
BUFSIZE The maximum number of bytes to be buffered per file.
BLOCKSIZE The desired block size for large data transfers.
These fields are updated when a job produces a checkpoint or completes. If a job has not yet produced a checkpoint, this information is not
available.
If the -cputimeoption is specified, the RUN_TIME column is replaced with:
CPU_TIME
The remote CPU time accumulated by the job to date (which has been stored in a checkpoint) in days, hours, minutes, and seconds. (If the
job is currently running, time accumulated during the current run is notshown. If the job has not produced a checkpoint, this column
contains 0+00:00:00.)
The -analyzeoption 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_REQUIREMENTS expression. If the -longoption is specified along with the -analyzeoption, the reason for fail-
ure is displayed on a per machine basis.
Options
-help
Get a brief description of the supported options
-global
Get queues of all the submitters in the system
-debug
Causes debugging information to be sent to stderr , based on the value of the configuration variable TOOL_DEBUG
-submitter submitter
List jobs of specific submitter from all the queues in the pool
-pool centralmanagerhostname[:portnumber]
Use the centralmanagerhostnameas the central manager to locate schedds. (The default is the COLLECTOR_HOST specified in the configura-
tion file.
-analyze
Perform an analysis to determine how many resources are available to run the requested jobs. These results are only meaningful for jobs
using Condor's matchmaker. This option is never meaningful for Scheduler universe jobs and only meaningful for grid universe jobs doing
matchmaking.
-run
Get information about running jobs.
-hold
Get information about jobs in the hold state. Also displays the time the job was placed into the hold state and the reason why the job
was placed in the hold state.
-globus
Get information only about jobs submitted to grid resources described as gt2or gt5.
-goodput
Display job goodput statistics.
-io
Display job input/output summaries.
-dag
Display DAG node jobs under their condor_dagmaninstance. Child nodes are listed using indentation to show the structure of the DAG.
-name name
Show only the job queue of the named schedd
-long
Display job ads in long format
-xml
Display job ads in xml format. The xml format is fully defined at http://www.cs.wisc.edu/condor/classad/refman/.
-attributes Attr1 [,Attr2 ... ]
Explicitly list the attributes (by name, and in a comma separated list) which should be displayed when using the -xmlor -longoptions.
Limiting the number of attributes increases the efficiency of the query.
-format fmt attr
Display attribute or expression attrin format fmt. To display the attribute or expression the format must contain a single printf(3)
-style conversion specifier. Attributes must be from the job ClassAd. Expressions are ClassAd expressions and may refer to attributes in
the job ClassAd. If the attribute is not present in a given ClassAd and cannot be parsed as an expression, then the format option will
be silently skipped. The conversion specifier must match the type of the attribute or expression. %s is suitable for strings such as
Owner , %d for integers such as ClusterId , and %f for floating point numbers such as RemoteWallClockTime . %v identifies the type of
the attribute, and then prints the value in an appropriate format. %V identifies the type of the attribute, and then prints the value in
an appropriate format as it would appear in the -longformat. As an example, strings used with %V will have quote marks. An incorrect
format will result in undefined behavior. Do not use more than one conversion specifier in a given format. More than one conversion
specifier will result in undefined behavior. To output multiple attributes repeat the -formatoption once for each desired attribute.
Like printf(3) style formats, one may include other text that will be reproduced directly. A format without any conversion specifiers
may be specified, but an attribute is still required. Include n to specify a line break.
-cputime
Instead of wall-clock allocation time (RUN_TIME), display 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 notshown.)
-currentrun
Normally, RUN_TIME contains all the time accumulated during the current run plus all previous runs. If this option is specified,
RUN_TIME only displays the time accumulated so far on this current run.
-avgqueuetime
Display the average of time spent in the queue, considering all jobs not completed (those that do not have JobStatus == 4 or JobStatus
== 3 .
-jobads file
Display jobs from a list of ClassAds from a file, instead of the real ClassAds from the condor_schedddaemon. This is most useful for
debugging purposes. The ClassAds appear as if condor_q -lis used with the header stripped out.
-machineads file
When doing analysis, use the machine ads from the file instead of the ones from the condor_collectordaemon. This is most useful for
debugging purposes. The ClassAds appear as if condor_status-lis used.
-stream-results
Display results as jobs are fetched from the job queue rather than storing results in memory until all jobs have been fetched. This can
reduce memory consumption when fetching large numbers of jobs, but if condor_q is paused while displaying results, this could result in
a timeout in communication with condor_schedd.
-wide
If this option is specified, and the command portion of the output would cause the output to extend beyond 80 columns, display beyond
the 80 columns.
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 ownerrestrictions are supplied, the job
matches the list only if it also matches an ownerrestriction.
General Remarks
The default output from condor_qis formatted to be human readable, not script readable. In an effort to make the output fit within 80 char-
acters, values in some fields might be truncated. Furthermore, the Condor Project can (and does) change the formatting of this default out-
put as we see fit. Therefore, any script that is attempting to parse data from condor_qis strongly encouraged to use the -formatoption
(described above, examples given below).
Although -analyzeprovides 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.
-goodput, -cputime, and -ioare most useful for STANDARD universe jobs, since they rely on values computed when a job checkpoints.
It is possible to to hold jobs that are in the X state, to avoid this it is best to construct a -constraint expressionthat contains 'Job-
Status != 3' if the user wishes to avoid this condition.
Examples
The -formatoption provides a way to specify both the job attributes and formatting of those attributes. There must be only one conversion
specification per -formatoption. As an example, to list only Jane Doe's jobs in the queue, choosing to print and format only the owner of
the job, the command line arguments for the job, and the process ID of the job:
%condor_q -submitter jdoe -format "%s" Owner -format " %s " Args -format "ProcId = %d
" ProcId
jdoe 16386 2800 ProcId = 0
jdoe 16386 3000 ProcId = 1
jdoe 16386 3200 ProcId = 2
jdoe 16386 3400 ProcId = 3
jdoe 16386 3600 ProcId = 4
jdoe 16386 4200 ProcId = 7
To display only the JobID's of Jane Doe's jobs you can use the following.
%condor_q -submitter jdoe -format "%d." ClusterId -format "%d
" ProcId
27.0
27.1
27.2
27.3
27.4
27.7
An example that shows the difference (first set of output) between not using an option to condor_qand (second set of output) using the
-globusoption:
ID OWNER SUBMITTED RUN_TIME ST PRI SIZE CMD
100.0 smith 12/11 13:20 0+00:00:02 R 0 0.0 sleep 10
1 jobs; 0 idle, 1 running, 0 held
ID OWNER STATUS MANAGER HOST EXECUTABLE
100.0 smith ACTIVE fork grid.example.com /bin/sleep
Exit Status
condor_qwill exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.
Author
Condor Team, University of Wisconsin-Madison
Copyright
Copyright (C) 1990-2012 Condor Team, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved.
Licensed under the Apache License, Version 2.0.
See the Condor Version 7.8.2 Manualor http://www.condorproject.org/licensefor additional notices. condor-admin@cs.wisc.edu
September 2012 condor_q(1)