10.3 Resource Usage Limits

Resource usage limits constrain the amount of resources a given job may consume. These limits are generally proportional to the resources requested and may include walltime, any standard resource, or any specified generic resource. The parameter RESOURCELIMITPOLICY controls which resources are limited, what limit policy is enforced per resource, and what actions the scheduler should take in the event of a policy violation.

10.3.1 Configuring Actions

The RESOURCELIMITPOLICY parameter accepts a number of policies, resources, and actions using the format and values defined below.

Note If walltime is the resource to be limited, be sure that the resource manager is configured to not interfere if a job surpasses its given walltime. For TORQUE, this is done by using $ignwalltime in the configuration on each mom node.



Resource Description
Maximum total job proc-seconds used by any single job (allows scheduler enforcement of cpulimit).
Local disk space (in MB) used by any single job task.
Maximum real memory/RAM (in MB) used by any single job.
NoteJOBMEM will only work with the MAXMEM flag.
Maximum processor load associated with any single job.
Maximum real memory/RAM (in MB) used by any single job task.
Minimum processor load associated with any single job (action taken if job is using 5% or less of potential CPU usage).
Maximum network load associated with any single job task.
Maximum processor load associated with any single job task.
Maximum virtual memory/SWAP (in MB) used by any single job task.
Requested job walltime.
Policy Description
take action whenever a violation is detected
take action only if a violation is detected and persists for greater than the specified time limit
take action only if a violation is detected and the constrained resource is required by another job
Action Description
terminate the job
checkpoint and terminate job
requeue the job and require a different set of hosts for execution
notify admins and job owner regarding violation
terminate and requeue the job
suspend the job and leave it suspended for an amount of time defined by the X parameter

Example - Notify and then cancel job if requested memory is exceeded

# if job exceeds memory usage, immediately notify owner
# if job exceeds memory usage for more than 5 minutes, cancel the job

Example - Checkpoint job on walltime violations

# if job exceeds requested walltime, checkpoint job
# when checkpointing, send term signal, followed by kill 1 minute later

Example - Cancel jobs that use 5% or less of potential CPU usage for more than 5 minutes


Example - Migrating a job when it blocks other workload


10.3.2 Specifying Hard and Soft Policy Violations

Moab is able to perform different actions for both hard and soft policy violations. In most resource management systems, a mechanism does not exist to allow the user to specify both hard and soft limits. To address this, Moab provides the RESOURCELIMITMULTIPLIER parameter that allows per partition and per resource multiplier factors to be specified to generate the actual hard and soft limits to be used. If the factor is less than one, the soft limit will be lower than the specified value and a Moab action will be taken before the specified limit is reached. If the factor is greater than one, the hard limit will be set higher than the specified limit allowing a buffer space before the hard limit action is taken.

In the following example, job owners will be notified by email when their memory reaches 100% of the target, and the job will be canceled if it reaches 125% of the target. For wallclock usage, the job will be requeued when it reaches 90% of the specified limit if another job is waiting for its resources, and it will be checkpointed when it reaches the full limit.


10.3.3 Constraining Walltime Usage

While Moab constrains walltime using the parameter RESOURCELIMITPOLICY like other resources, it also allows walltime exception policies which are not available with other resources. In particular, Moab allows jobs to exceed the requested wallclock limit by an amount specified on a global basis using the JOBMAXOVERRUN parameter or on a per credential basis using the OVERRUN attribute of the *CFG credential parameters.

CLASSCFG[debug]  overrun=00:00:30  

See Also

Copyright © 2012 Adaptive Computing Enterprises, Inc.®