Spectrum LSF

Showing 486 of 15091

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...

11 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...

11 months ago in Spectrum LSF / Administration 0 Future consideration

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 ...

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

3 VOTE

Add IBM LSF RTM alert interval by weekly basis, currently it only has daily alert notice in RTM pop-up column.

IBM Spectrum LSF RTM only have hours, daily basis of alert pop-up column could choose. For management of current alert aggregation, We need IBM to add this feature enhancement into RTM fix patch. The features enhancement came from needs of...

almost 3 years ago in Spectrum LSF / Operations/RTM 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?

12 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.

12 months ago in Spectrum LSF / Administration 0 Future consideration

2 VOTE

bjobs -o reserved_mem or bhosts -o reserved_mem

To see how much memory is reserved on a host, we need to parse the bhosts -l <hostname> command, and it doesn't give us info about which job is reserving how much memory. I'd either like to see one of the following: bhosts -o 'jobid reserved...

almost 2 years ago in Spectrum LSF / Scheduling 1 Future consideration

8 VOTE

Increase MAX_JOBID in PE environment - 4194303 too low

When using PE in LSF the maximum job ID is 4194303.We have already cycled through the range in 12 months and we'll likely do it twice this year.Having jobs with duplicate IDs causes a lot of problems with things like job accounting.

over 7 years ago in Spectrum LSF 1 Not under 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 ...

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

2 VOTE

Show unformatted pending reasons with bjobs -UF

Information for PENDING REASONS remains formatted for the command "bjobs -UF [-p|-p0|-p1|-p2|-p3] <jobid>" which makes it hard for scripts to parse the output. Current output: $: bjobs -UF -p3 <jobid> ... PENDING REASONS: Candidate hos...

almost 2 years ago in Spectrum LSF / Reporting/Explorer 0 Future consideration

Please enter your email address

FILTER BY CATEGORY