Each Grid Engine queue restricts what kinds of jobs it will accept, and this is summarized under the “qtype” (or queue type) heading. In addition, it displays information about the queue instances and the host associated with the queue instance. The host-centric view displays per-job information similar to that which the job-centric view provided. One helpful feature of displaying jobs in host-centric fashion is that parallel jobs that span multiple hosts will be displayed under each queue instance in which they run: the “RhDimer1” job in the example above uses 28 slots across the n015 and n016 hosts. The -ne option is also useful in this regard: it filters the qstat -f output to only those queue instances with jobs that are executing.Īs with the job-centric display method, the -u flag can be used to affect what user(s) jobs are displayed. The argument to -q is a queue or queue instance name, and may contain wildcard (*) characters as demonstrated here: it_css* = all queue instances whose name starts with it_css. Without the -q option, the command would have displayed information for every queue instance (and there are many queue instances). The output from qstat -f is organized by queue instances (thus, also by compute hosts) with jobs running in a particular queue instance summarized therein: To instead view the status information in a host-centric format, the -f option should be added to the qstat command. In all forms discussed above the output from qstat focuses on jobs. Specifying the wildcard argument displays job status for all cluster users. The flag requires a single argument: a username or the wildcard character ( \*): The qstat command also allows the user to see job status information for any other cluster user by means of the -u flag. See Using Job Holds for more information. Job has completed and is being deleted from its queue.ĭisplayed when a hold has been placed on a job, such that other jobs must complete before it can begin. Job has been suspended so that a higher-priority job can preempt it and use its resources. Jobs usually go from t to r quickly, but very large parallel jobs may persist in t for a short time.Īn error occurred when Grid Engine attempted to schedule the job, so it has been returned to the qw state Job is ready to execute and is transferring to its assigned node.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |