Spectrum LSF

Showing 66

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

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

Support RUN_TIME_DECAY on GPU Runtime

Currently RUN_TIME_DECAY only modifies Fairshare for CPU jobs and not GPU jobs.

8 months ago in Spectrum LSF / Administration 0 Future consideration

1 VOTE

lsfproxyd - Persistent blocking rules

LSFProxyd is a new solution to help scheduler handle queries effectively. This RFE is to enable persistent blocksing rules for heavy query hitters. Same has been discussed with John Welch in a separate discussion.

8 months ago in Spectrum LSF / Scheduling 1 Future consideration

2 VOTE

Allow to set/modify the same option in multiple esubs

Currently a specific option can only be set or modified once through an esub, even if multiple esub's are run. If an option is set a second time, the error message ... Conflict parameter <PARAMETER_NAME> - Ignored. appears. There are at leas...

9 months ago in Spectrum LSF / Administration 1 Future consideration

2 VOTE

Expand API (or bjobs -o option) to report memory reservation on a per-job basis

Determining per-job memory usage is valuable, but we also need to be able to see, on a per-job basis, how much memory job(s) have reserved at a point in time. Partly we need to be able to compare to the actual memory use to see if they're over-res...

9 months ago in Spectrum LSF / Scheduling 0 Future consideration

1 VOTE

Add additional bhist information about personnel who modified the LSF job

Enhance bhist to show who modifies the job. The information is not presented in JOB_MODIFY2 event record. Current user info in JOB_MODIFY2 is job owner and user auth for remote job in MC

10 months ago in Spectrum LSF / Administration 0 Future consideration

3 VOTE

Allow Flagging Jobs for Reservation Through Rules and/or Through a "bsub --plan" Option

Today, reservations in LSF are handled by the Top X jobs by ordered by Dynamic Priority using the variable MAX_JOB_RESERVE. We believe that this is a shotgun approach. We have millions of jobs a day that require 1 cores and less than 1GB of memory...

11 months ago in Spectrum LSF / Administration 0 Future consideration

1 VOTE

badmin appclose/appopen for maintenance of a specific application

For maintenance reasons it would be helpful to close/open applications for dispatching like for queues and hosts by the command badmin qclose/qopen and badmin hclose/hopen respectively.

11 months ago in Spectrum LSF / Administration 1 Future consideration

Please enter your email address

FILTER BY CATEGORY