Current State

7 Day History

Notes

In some cases multiple queues draw from the same pool of nodes, and MSI throttles each queue (using a fairshare system) to ensure that jobs from one queue don't hog all of the nodes in the shared pool. It is not possible to determine how many nodes are busy and available in the individual queues. In these cases the number of busy and available nodes are shown for the pool of nodes, and listed under one queue name:

• Mangi: The mangi queue is a meta-queue, which automatically routes jobs to the amdsmall and amdlarge queues, which all draw from the same pool of nodes.
• Agate: The agate queue is a meta-queue, which automatically routes jobs to the agsmall and aglarge queues, which all draw from the same pool of nodes.

• Idle: Entire node is available to run a job
• Running: Some but not all resources (memory and CPUs) on the node are allocated to one or more jobs
• Busy: All resources (memory and/or CPUs) on the node are allocated to one or more jobs
• Down: The node is not running a job and is not available to run a job

Note that the scheduler may not assign a job to an idle node, if nodes are reserved for an upcoming maintenance day or idle nodes are being accumulated for a large job, for example. The down state indicates the node has crashed, is offline for maintenance, or is not available for other reasons.