abstract:farber:runjobs:job_status

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
abstract:farber:runjobs:job_status [2018-12-01 11:44] anitaabstract:farber:runjobs:job_status [2021-10-13 16:49] (current) – [Per-Group QStat and QHost] anita
Line 1: Line 1:
-====== Managing jobs on Farber ======+====== Managing Jobs on Farber ======
  
 Once a user has been able to submit jobs to the queue -- interactive or batch -- the user will from time to time want to know what those jobs are doing.  Is the job waiting in a queue for resources to become available, or is it executing?  How long has the job been executing?  How much CPU time or memory has the job consumed?  Users can query Grid Engine for job information using the ''qstat'' command.  The ''qstat'' command has a variety of command line options available to customize and filter what information it displays; discussing all of them is beyond the scope of this document.  Please see the ''qstat'' man page for a detailed description of all options. Once a user has been able to submit jobs to the queue -- interactive or batch -- the user will from time to time want to know what those jobs are doing.  Is the job waiting in a queue for resources to become available, or is it executing?  How long has the job been executing?  How much CPU time or memory has the job consumed?  Users can query Grid Engine for job information using the ''qstat'' command.  The ''qstat'' command has a variety of command line options available to customize and filter what information it displays; discussing all of them is beyond the scope of this document.  Please see the ''qstat'' man page for a detailed description of all options.
Line 195: Line 195:
 The ''qstatgrp'' command by default summarizes usage of all queues to which the user has access given his/her current working group.  Adding the ''-j'' flag summarizes the jobs executing in those queues rather than summarizing the queues themselves. The ''qstatgrp'' command by default summarizes usage of all queues to which the user has access given his/her current working group.  Adding the ''-j'' flag summarizes the jobs executing in those queues rather than summarizing the queues themselves.
  
-The ''qhostgrp'' command by default summarizes usage of all hosts to which the user has access given his/her current working group.  Adding the ''-j'' flag summarizes the jobs (including [[general/jobsched/standby|standby]]) executing on those hosts rather than summarizing the hosts themselves.+The ''qhostgrp'' command by default summarizes usage of all hosts to which the user has access given his/her current working group.  Adding the ''-j'' flag summarizes the jobs (including [[abstract:farber:runjobs:queues#farber-standby-queues|standby]]) executing on those hosts rather than summarizing the hosts themselves.
  
 Both ''qstatgrp'' and ''qhostgrp'' accept a ''-g ''<<''group name''>> option to limit to an arbitrary group (and not just the user's current working group). Both ''qstatgrp'' and ''qhostgrp'' accept a ''-g ''<<''group name''>> option to limit to an arbitrary group (and not just the user's current working group).
  • abstract/farber/runjobs/job_status.1543682643.txt.gz
  • Last modified: 2018-12-01 11:44
  • by anita