Platform LSF Administration Guide Version 6.2

Chapter 29
Runtime Resource Usage Limits
Administering Platform LSF
463
Priority of resource usage limits
If no limit is specified at job submission, then the following apply to all jobs submitted
to the queue:
Incorrect resource usage limits
Incorrect limits are ignored, and a warning message is displayed when the cluster is
reconfigured or restarted. A warning message is also logged to the
mbatchd log file
when LSF is started.
If no limit is specified at job submission, then the following apply to all jobs submitted
to the queue:
Resource usage limits specified at job submission must be less than the maximum
specified in
lsb.queues. The job submission is rejected if the user-specified limit is
greater than the queue-level maximum, and the following message is issued:
Cannot exceed queue’s hard limit(s). Job not submitted.
Enforcing limits on chunk jobs
By default, resource usage limits are not enforced for chunk jobs because chunk jobs are
typically too short to allow LSF to collect resource usage.
To enforce resource limits for chunk jobs, define LSB_CHUNK_RUSAGE=Y in
lsf.conf. Limits may not be enforced for chunk jobs that take less than a minute to
run.
If ... Then ...
Both default and maximum limits are defined The default is enforced
Only a maximum is defined The maximum is enforced
No limit is specified in the queue or at job submission No limits are enforced
If ... Then ...
The default limit is not correct The default is ignored and the maximum limit is enforced
Both default and maximum limits
are specified, and the maximum is
not correct
The maximum is ignored and the resource has no
maximum limit, only a default limit
Both default and maximum limits
are not correct
The default and maximum are ignored and no limit is
enforced