Add a 'bsub -Gl limit_name' option to separate Fairshare Assignment from the Limit also add a default limit pattern to use if ONE_UG_TREE does not find a matching limit

We have many cases, where we have limits for users, but we also want to want to apply a fairshare group for the job to arrive at a base allocation. Unfortunately, with ONE_UG enabled, if the Fairshare Group does not have a corresponding Limit, not limits are applied to the job. With ONE_UG disabled, there is not guarantee as to which limit will be used and this have a huge impact when the user belongs to multiple limits.

We would like two things to work around these limitations.

1) Allow us to specify the Limit Group to apply to the job using the -Gl
2) If the -Gl is not specified, and there is no corresponding limit in the bsub -G, find the closest match limit for a user that matches a pattern.

For 2) we have limits labeled as follows:

normal.jlu.1500 # Normal queue Job Limit User 1500 slots/jobs
normal.jlu.2500 # Normal queue Job Limit User 2500 slots/jobs

A user will be mapped to at most one of these job limit patterns. So, it would be nice to have something like the following in lsb.params

DEFAULT_JOB_LIMIT=*.jlu.*

Needed By

Yesterday (Let's go already!)

Post comment

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Please enter your email address

RELATED IDEAS

Add a 'bsub -Gl limit_name' option to separate Fairshare Assignment from the Limit also add a default limit pattern to use if ONE_UG_TREE does not find a matching limit