Limit conflicts

For similar limits configured in lsb.resources, lsb.users, lsb.hosts, or lsb.queues, the most restrictive limit is used. For example, a slot limit of 3 for all users is configured in lsb.resources:

Begin Limit
NAME  = user_limit1
USERS = all
SLOTS = 3
End Limit

This is similar, but not equivalent to an existing MAX_JOBS limit of 2 is configured in lsb.users.

busers
USER/GROUP    JL/P    MAX  NJOBS   PEND    RUN  SSUSP  USUSP    RSV 
user1           -       2      4      2      2      0      0      0

user1 submits 4 jobs:

bjobs
JOBID   USER    STAT  QUEUE     FROM_HOST   EXEC_HOST   JOB_NAME   SUBMIT_TIME
816     user1   RUN   normal    hostA       hostA       sleep 1000 Jan 22 16:34
817     user1   RUN   normal    hostA       hostA       sleep 1000 Jan 22 16:34
818     user1   PEND  normal    hostA                   sleep 1000 Jan 22 16:34
819     user1   PEND  normal    hostA                   sleep 1000 Jan 22 16:34

Two jobs (818 and 819) remain pending because the more restrictive limit of 2 from lsb.users is enforced:

bjobs -p
JOBID   USER    STAT  QUEUE      FROM_HOST      JOB_NAME           SUBMIT_TIME
818     user1   PEND  normal     hostA          sleep 1000         Jan 22 16:34
The user has reached his/her job slot limit;
819     user1   PEND  normal     hostA          sleep 1000         Jan 22 16:34
The user has reached his/her job slot limit;

If the MAX_JOBS limit in lsb.users is 4:

busers
USER/GROUP  JL/P   MAX  NJOBS   PEND   RUN  SSUSP  USUSP  RSV
user1         -      4      4      1     3      0      0    0

and user1 submits 4 jobs:

bjobs
JOBID  USER    STAT  QUEUE   FROM_HOST   EXEC_HOST    JOB_NAME     SUBMIT_TIME
824    user1   RUN   normal  hostA       hostA        sleep 1000   Jan 22 16:38
825    user1   RUN   normal  hostA       hostA        sleep 1000   Jan 22 16:38
826    user1   RUN   normal  hostA       hostA        sleep 1000   Jan 22 16:38
827    user1   PEND  normal  hostA                    sleep 1000   Jan 22 16:38

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;

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