This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Employees should enter Ideas at https://ideas.ibm.com
See this idea on ideas.ibm.com
The current LSF preemption design does not prevent over-preemption (i.e. preempt more jobs than needed). When the preemption of a large low job takes some time like several minutes, the following incoming high priority jobs could preempt other running jobs even if the ongoing preemption would release enough resource for them eventually.
We hope over-preemption can be prevented. Scheduler can check if the resources to be released by the ongoing preemptions is enough for the incoming high priority jobs. If it is, then preemption will not be triggered immediately for the high priority jobs, they will wait for some configurable time for the finish of the ongoing preemptions, and preempt only when the timer expires.
Below is an example of over-preemption. There are 3 queues with priorities prod > preprod > devonprod. "JOB_CONTROLS=TERMINATE[SIGTERM]" and "TERMINATE_WHEN=PREEMPT" are set in the queues.
J1: bsub -q preprod -n 3 sleep 2000
J2: bsub -q preprod -n 3 sleep 2000
J3: bsub -n 30 -q devonprod "sh /scratch/support/gordonc/tmp/trap.sh" <<< the preemption of this job would take 100sec
Following jobs are submitted after J 1 ~ 3 are running
J4: bsub -q prod sleep 1000
J5: bsub -q prod sleep 1000
J6: bsub -q prod sleep 1000
J7: bsub -q prod sleep 1000
J8: bsub -q prod sleep 1000
J9: bsub -q prod sleep 1000
J4 would preempt J3. Some jobs among J5~9 would preempt J1 and/or J2, and eventually J3 will be preempted too.
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.
The observed behavior, while undesirable in your situation, is correct. If a job is taking too long to free up resources, the scheduler will try to get the resources from elsewhere.
As an alternative, have you considered using the Planner capability that was released in LSF 10 Service Pack 6? This effectively makes the scheduler more deterministic/less aggressive, and will ensure that once a decision is made to schedule a job on resource ABC, it will stick to that decision, even if it is less optimal.
https://www.ibm.com/support/knowledgecenter/SSWRJV_10.1.0/lsf_release_notes/lsf_relnotes_jobschedulingexecution10.1.0.6.html