LSF Version 7.3 - Platform LSF Configuration Reference

Description
Resource requirements used to determine eligible hosts. Specify a resource requirement string
as usual. The resource requirement string lets you specify conditions in a more flexible manner
than using the load thresholds.
The select section defined at the queue level must be satisfied at in addition to any job-level
requirements or load thresholds.
The rusage section can specify additional requests. To do this, use the OR (||) operator to
separate additional rusage strings.
When both job-level and queue-level rusage sections are defined, the rusage section defined
for the job overrides the rusage section defined in the queue. The two rusage definitions are
merged, with the job-level rusage taking precedence.
For example:
Queue-level
RES_REQ:
RES_REQ=rusage[mem=200:lic=1] ...
For the job submission:
bsub -R'rusage[mem=100]' ...
the resulting requirement for the job is
rusage[mem=100:lic=1]
where mem=100 specified by the job overrides mem=200 specified by the
queue. However, lic=1 from queue is kept, since job does not specify it.
Queue-level
RES_REQ
with decay and
duration
defined:
RES_REQ=rusage[mem=200:duration=20:decay=1] ...
For a job submission with no decay or duration:
bsub -R'rusage[mem=100]' ...
the resulting requirement for the job is:
rusage[mem=100:duration=20:decay=1]
Queue-level duration and decay are merged with the job-level specification,
and mem=100 for the job overrides mem=200 specified by the queue.
However, duration=20 and decay=1 from queue are kept, since job does
not specify them.
When LSF_STRICT_RESREQ=Y in lsf.conf, LSF rejects resource requirement strings
where an rusage section contains a non-consumable resource
The order section defined at the queue level is ignored if any resource requirements are
specified at the job level (if the job-level resource requirements do not include the order
section, the default order, r15s:pg, is used instead of the queue-level resource requirement).
If RES_REQ is defined at the queue level and there are no load thresholds defined, the pending
reasons for each individual load index are not displayed by bjobs.
The span section defined at the queue level is ignored if the span section is also defined at
the job level or in an application profile.
Note:
Define span[hosts=-1] in the application profile or in bsub R
resource requirement string to override the span section setting
in the queue.
lsb.queues
Platform LSF Configuration Reference 315