Difference between revisions of "HOWTO check up on jobs"
From HPC
m (→Asking MAUI when your job will probably start and finish) |
m |
||
| Line 1: | Line 1: | ||
== Examining the queue == | == Examining the queue == | ||
| − | + | You can look at the queue by using the <code>qstat</code> command. <code>qstat</code> will display the queue ordered by JobID. | |
<pre> | <pre> | ||
| − | [username@launch ~]$ | + | [username@launch ~]$ qstat |
| − | + | Job id Name User Time Use S Queue | |
| − | + | ---------------- ---------------- ---------------- -------- - ----- | |
| − | + | 32.pbsserver JobName username 351:04:3 R long | |
| − | + | 33.pbsserver JobName username 351:06:1 R day | |
| − | + | 34.pbsserver JobName username 390:30:2 R week | |
| − | + | 40.pbsserver JobName username 496:38:2 R month | |
| − | + | 46.pbsserver JobName username 506:13:5 R long | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
</pre> | </pre> | ||
== Checking a specific job == | == Checking a specific job == | ||
| − | If you want to see the details of a specific job, use <code> | + | If you want to see the details of a specific job, use <code>qstat -f <JobID></code> on it: |
<pre> | <pre> | ||
| − | [username@launch ~]$ | + | [username@launch ~]$ qstat -f 40 |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
</pre> | </pre> | ||
| Line 82: | Line 36: | ||
There's no output on a successful job deletion. Keep in mind that running jobs are killed, '''files in scratch space will not sync back to your home directory''' and that '''scratch space will not be cleaned'''. If you delete running jobs that use scratch space, please let the administrator know to check for dirty scratch spaces. | There's no output on a successful job deletion. Keep in mind that running jobs are killed, '''files in scratch space will not sync back to your home directory''' and that '''scratch space will not be cleaned'''. If you delete running jobs that use scratch space, please let the administrator know to check for dirty scratch spaces. | ||
| − | + | <!-- | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Overview of cluster usage == | == Overview of cluster usage == | ||
| Line 104: | Line 47: | ||
comp002 excl 3.8 1877 4 5907 409 4/1 4 0 33 username 35 username 37 username 39 username | comp002 excl 3.8 1877 4 5907 409 4/1 4 0 33 username 35 username 37 username 39 username | ||
</pre> | </pre> | ||
| + | --> | ||
Revision as of 14:09, 12 January 2016
Examining the queue
You can look at the queue by using the qstat command. qstat will display the queue ordered by JobID.
[username@launch ~]$ qstat Job id Name User Time Use S Queue ---------------- ---------------- ---------------- -------- - ----- 32.pbsserver JobName username 351:04:3 R long 33.pbsserver JobName username 351:06:1 R day 34.pbsserver JobName username 390:30:2 R week 40.pbsserver JobName username 496:38:2 R month 46.pbsserver JobName username 506:13:5 R long
Checking a specific job
If you want to see the details of a specific job, use qstat -f <JobID> on it:
[username@launch ~]$ qstat -f 40
If you want to look at the output of your job while it's still running, use the qpeek command.
[username@launch ~]$ qpeek 40
Deleting a job you no longer want
If you want to delete a job (whether it's already running or not), use the qdel command:
[username@launch ~]$ qdel 41
There's no output on a successful job deletion. Keep in mind that running jobs are killed, files in scratch space will not sync back to your home directory and that scratch space will not be cleaned. If you delete running jobs that use scratch space, please let the administrator know to check for dirty scratch spaces.
