Spectrum LSF

Showing 478

LSF doesn't allow multiple LOAN policies on the same hosts

LSF has limitation in SLA LOAN_POLICIES configuration by having only one loan duration time available. It would be great, if SLA LOAN_POLICIES can support option to LOAN for different time to different queues. For example:LOAN_POLICIES = QUEUES[ge...

over 3 years ago in Spectrum LSF / Administration 1 Not under consideration

2 VOTE

RTM to/from LSF communication of Psusp-requeue job notifcation

We have reproduced the issue and it's a timing issue with RTM because LSF does not provide exitinfo when job's pre-exec fails and requeued. Since RTM relies on exitinfo to put it in the correct table, the changes will have to come from LSF. This w...

over 3 years ago in Spectrum LSF / Operations/RTM 0 Not under consideration

3 VOTE

bjgroup: option to select user (OWNER)

add -u option to bjgroup command to filter output by OWNER. show only user jobgroup for a given user (like bjobs), used '-u all' to show all.

over 5 years ago in Spectrum LSF 1 Not under consideration

1 VOTE

allow update for span string after a job is started

Hello, currently, it's not possible to update the span string after a job is started. for ex: a user start a multinodes jobs using bsub .... -n x -R ".. span[ptile=y]" ... unfortunately, he forgot to specify to the tool to start in mutlinodes an...

almost 2 years ago in Spectrum LSF / Scheduling 1 Not under consideration

3 VOTE

preemption

We're going to use the preemption through the following settings. Begin QueueQUEUE_NAME = test99PRIORITY = 99HOSTS = allPREEMPTION = PREEMPTIVE[test1]End Queue Begin QueueQUEUE_NAME = test1PRIORITY = 1HOSTS = allPREEMPTION = PREEMPTABLE[test99]TER...

over 5 years ago in Spectrum LSF 1 Not under consideration

3 VOTE

bkill instrumentation/logging to find source

Currently the bkill command only tracks (lsb.events) who ran it, and what signal was sent. If we have a heavily active user with a broken script, it is very challenging to find the source of the bkill command. It would be valuable to log the sourc...

over 5 years ago in Spectrum LSF 1 Not under consideration

1 VOTE

Preemption support for MIG GPU jobs

We would like that preemption will be supported also for MIG jobs(A100 dgx mig devices). Currently the preemption is not working for this type of jobs. Example scenatiois: kill two or more jobs and reconfigure mig to have the new job run. We need ...

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

1 VOTE

Allow bjobs command to show the pre and post exec exitStatus/exitCode information

Right now, we require bhist to get any detail on pre/post exec error codes, it would be nice if we could get this from the job record via bjobs vs. bhist. bhist in very large environments is a non-starter for obtaining this status information.

almost 2 years ago in Spectrum LSF / Administration 1 Not under consideration

1 VOTE

Allow Users to specify a ClearCase 'cleartool' command but require that it be white listed first

Allow the users to override the CLEARTOOL binary path, but only if it's included in a white list configuration file in the $LSF_ENVDIR location. I would suggest something like: cat lsf.daemons.wrap.conf /usr/altira/bin/cleartool /some/authorized/...

almost 2 years ago in Spectrum LSF / Administration 1 Not under consideration

1 VOTE

Set more job variables in parent SBATCHD prior to forking the job SBATCHD/RES

I've been working with the Daemons Wrap source code trying to make the logging more presentable, and I've come accross a hurdle to effectively enhancing that integration. I need both the Job Start and Submit Times, and normally, I would just be ab...

almost 2 years ago in Spectrum LSF / Administration 1 Not under consideration

Please enter your email address

FILTER BY CATEGORY