Spectrum LSF

Showing 475

Correct on Design Flaw in Session Scheduler

Currently the Session Manager and Service Director operate in the same CGROUP on the first execution host which causes a race condition that if a task on the first execution host pushes the memory use above the memory limit (aka mem-eater process)...

6 months ago in Spectrum LSF / Scheduling 1 Not under consideration

1 VOTE

Allow the LSF Planner to ignore cetain select[] criteria

The current LSF Planner is unable to create a plan if the "bsub -R "select[blah>blah]" ./a.out" select clause does not match any hosts. This is very counter productive. For certain ELIM based resources such as 'freescratch', 'freetmp', etc. The...

6 months ago in Spectrum LSF / Administration 0 Future consideration

1 VOTE

Allow the INELIBIBLE flag to apply to Job Slots and License Scheduler Limits

Currently, the INELIGIBLE flag works for several limit classes. Unfortunately, it does not support either SLOT or License Project limits. These are important for using APS with ELIGIBLE pending time calculations and the queue limit of ELIGIBLE_PEN...

6 months ago in Spectrum LSF / Administration 0 Future consideration

2 VOTE

Allow resource limit ELIGIBLE_PEND_JOBS usage for APPS

I would like to have a limit ELIGIBLE_PEND_JOBS for the consumer APPS. The reason is an application which needs licenses from a license server. In case of many simultanously dispatched jobs the license server overloads. Up to now the resource limi...

6 months ago in Spectrum LSF / Scheduling 1 Needs more information

2 VOTE

tool to list out active and default base params - lsparams

Think of 'bparams' and the level of details that it provides with args '-la'. This helps in figuring out what all params are configured as default or what defaults values are affecting the scheduling. Such a tool does not exist for LSF Base config...

6 months ago in Spectrum LSF / Scheduling 0 Planned for future release

1 VOTE

Adjust the priority of pending reason

If both license lack and limit(SLOTS, JOBS) reach together, the job pending reason shows license reason ONLY, not include limit. We want to adjust the priority of pending reason "limit(SLOTS, JOBS)" related pending reason is requested as high ...

6 months ago in Spectrum LSF / Administration 1 Not under consideration

1 VOTE

FLEXlm supports 'uncounted node locked' Feature Types Report the Checkouts for Them

By default RTM always report 0 max license and 0 in use. However, if you look at the checkouts, there are several in use. Can we get RTM to at least report the number of checked out licenses for this feature class?

7 months ago in Spectrum LSF / Operations/RTM 0 Future consideration

1 VOTE

Provide an Option to break out of 'bsub' if a job will not submit due to a user hitting their pending job limit

This is a major problem when using a web service to control jobs, you would much rather have the binary end with an exit code than continually block in a loop saying you have reached your pending jobs limit. It's really bad design behavior IMHO.

7 months ago in Spectrum LSF / Administration 0 Future consideration

1 VOTE

Clean left over job's daemon processes after job res finished

We have several workflows that the job script can run tools that will spawn processes in the backgroup or as daemons that will stay active once the job script ends. Since the job script ends, res will end with the exit code of the job script, but ...

7 months ago in Spectrum LSF / Other 3 Functionality already exists

2 VOTE

Group jobs to same cluster when using bsub -cluster feature

Goal: Group together lsf jobs, "regression", in such a way that bsub -cluster feature directs all jobs in the group to the same cluster. Proposal: a) bsub submits all jobs in a job array to a single cluster bsub -cluster all -J "ArrayName[1-10]" /...

7 months ago in Spectrum LSF / Scheduling 1

Please enter your email address

FILTER BY CATEGORY