next up previous contents index
Next: condor_ qedit Up: 9. Command Reference Manual Previous: condor_ prio   Contents   Index

Subsections


condor_ q

Display information about jobs in queue

Synopsis

condor_ q [-help]

condor_ q [-debug] [-global] [-submitter submitter] [-name name] [-pool centralmanagerhostname[:portnumber]] [-analyze] [-better-analyze] [-run] [-hold] [-globus] [-goodput] [-io] [-dag] [-long] [-xml] [-format fmt attr] [-cputime] [-currentrun] [-avgqueuetime] [-jobads file] [-machineads file] [-direct rdbms | quilld | schedd] [{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:

To restrict the display to jobs of interest, a list of zero or more restrictions may be supplied. Each restriction may be one of:

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 queried jobs by printing the entire job classad. The attributes of the job classad may be displayed by means of the -format option, which displays attributes with a printf(3) format. Multiple -format options may be specified in the option list to display several attributes of the job. If neither -long or -format are specified, condor_ q displays 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. 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.

If the -dag option is specified, the OWNER column is replaced with NODENAME for jobs started by Condor DAGMan.

NOTE: The -dag option has no effect on a pre-v6.3.0 Condor queue, because older condor_ schedd daemons don't pass the necessary DAG information to their jobs.

If the -run option is specified, the ST, PRI, SIZE, and CMD columns are replaced with:

HOST(S)
The host where the job is running. For PVM jobs, a host count is displayed instead.

If the -globus option 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 signal 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 -goodput option 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 -io option 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 -cputime option 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 not shown. If the job has not produced a checkpoint, this column contains 0+00:00:00.)

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_REQUIREMENTS expression. If the -long option is specified along with the -analyze option, the reason for failure is displayed on a per machine basis.

The -better-analyze option does a more thorough job of determining why jobs are not running than -analyze. There are scalability issues present when run on a pool with a large number of machines, as well as when run to analyze a large number of queued jobs. The -better-analyze option make take an excessively long time to complete in these cases. Therefore, it is recommended to constrain -better-analyze to only analyze one job at a time.

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 centralmanagerhostname 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. 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.
-better-analyze
Perform a more time-consuming, but potentially more extensive analysis to determine how many resources are available to run the requested jobs.
-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 gt2, gt3, or gt4.
-goodput
Display job goodput statistics.
-io
Display job input/output summaries.
-dag
Display DAG jobs under their DAGMan.
-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/.
-format fmt attr
Display attribute or expression attr in 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. 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 -format option once for each desired attribute. Like printf(3) style formats, you can include other text that will be reproduced directly. You can specify a format without any conversion specifiers but you must still give attribute. You can include $\mathtt{\backslash}$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 not shown.)
-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_ schedd daemon. This is most useful for debugging purposes. The ClassAds appear as if condor_ q -l is 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_ collector daemon. This is most useful for debugging purposes. The ClassAds appear as if condor_ status -l is used.
-direct rdbms | quilld | schedd
When the use of Quill is enabled, this option allows a direct query to either the rdbms, the condor_ quill daemon, or the condor_ schedd daemon for the requested queue information. It also prevents the queue location discovery algorithm from failing over to alternate sources of information for the queue in case of error. It is useful for debugging an installation of Quill. One of the strings rdbms, quilld, or schedd is required with this option.
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.

General Remarks

The default output from condor_ q is formatted to be human readable, not script readable. In an effort to make the output fit within 80 characters, values in some fields might be truncated. Furthermore, the Condor Project can (and does) change the formatting of this default output as we see fit. Therefore, any script that is attempting to parse data from condor_ q is strongly encouraged to use the -format option (described above, examples given below).

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.

-goodput, -cputime, and -io are most useful for STANDARD universe jobs, since they rely on values computed when a job checkpoints.

Examples

The -format option provides a way to specify both the job attributes and formatting of those attributes. There must be only one conversion specification per -format option. 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\n" 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\n" 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_ q and (second set of output) using the -globus option:

 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_ q will 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 © 1990-2007 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.8.7 Manual for additional notices.


next up previous contents index
Next: condor_ qedit Up: 9. Command Reference Manual Previous: condor_ prio   Contents   Index
condor-admin@cs.wisc.edu