Platform LSF Administration Guide Version 6.2

Configuring Resource Allocation Limits
Administering Platform LSF
336
Only one job (827) remains pending because the more restrictive limit of 3 in
lsb.resources is enforced:
% bjobs -p
JOBID USER STAT QUEUE FROM_HOST JOB_NAME SUBMIT_TIME
827 user1 PEND normal hostA sleep 1000 Jan 22 16:38
Resource (slot) limit defined cluster-wide has been reached;
Equivalent
conflicting limits
New limits in lsb.resources that are equivalent to existing limits in lsb.users,
lsb.hosts, or lsb.queues, but with a different value override the existing limits.
The equivalent limits in
lsb.users, lsb.hosts, or lsb.queues are ignored, and
the value of the new limit in
lsb.resources is used.
For example, a per-user job slot limit in
lsb.resources is equivalent to a
MAX_JOBS limit in
lsb.users, so only the lsb.resources limit is enforced, the
limit in
lsb.users is ignored:
Begin Limit
NAME = slot_limit
PER_USER =all
SLOTS = 3
End Limit
Example limit configurations
Each set of limits is defined in a Limit section enclosed by Begin Limit and End
Limit
.
Example 1
user1
is limited to 2 job slots on hostA, and user2’s jobs on queue normal are
limited to 20 MB of memory:
Begin Limit
HOSTS SLOTS MEM SWP TMP USERS QUEUES
hostA 2 - - - user1 -
- - 20 - - user2 normal
End Limit
Example 2
Set a job slot limit of 2 for user user1 submitting jobs to queue normal on host hosta
for all projects, but only one job slot for all queues and hosts for project
test:
Begin Limit
HOSTS SLOTS PROJECTS USERS QUEUES
hosta 2 - user1 normal
- 1 test user1 -
End Limit
Example 3
Limit usage of hosts in license1 group:
◆ 10 jobs can run from normal queue
◆ Any number can run from short queue, but only can use 200 MB of memory in
total
◆ Each other queue can run 30 jobs, each queue using up to 300 MB of memory in
total