Reference: Monitoring and Controlling Queues a – Load threshold alarm o – Orphaned A – Suspend threshold alarm C – Suspended by calendar D – Disabled by calendar S – Suspended by subordination to another queue c – Configuration ambiguous d – Disabled s – Suspended u – Unknown E – Error
For a queue that uses h_vmem as a resource: > qstat -F h_vmem queuename qtype resv/used/tot. load_avg arch states ——————————————————————————— all.q@compute-1-0.local BIP 0/0/12 0.05 lx26-amd64 hc:h_vmem=48.000G
Disable: # qmod -d all.q@compute-0-0.local workflow.q@compute-0-0.local Enable: # qmod -e all.q@compute-0-0.local workflow.q@compute-0-0.local
The contents of a basic Sun Grid Engine job file look something like this: #!/bin/bash # SGE uses shell script comments that start with “#$” to configure how # SGE handles the job. # # Use the bash shell as the shell for the job: #$ -S /bin/bash # # Write output and error stream [...]
The “qstat” command provides information on the state of Grid Engine machines and queues. Entering “qstat” alone gives a brief overview of jobs in the queue: > qstat job-ID prior name user state submit/start at queue slots ja-task-ID —————————————————————————————————————– 395 0.55500 run-DSL22- aleonard r 06/13/2007 15:59:18 all.q@compute-0-1.local 1 393 0.55500 run-DSL20- aleonard r 06/13/2007 15:59:18 [...]