Skip to Main Content
IBM Data and AI Ideas Portal for Customers


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,

  1. Post an idea

  2. Upvote ideas that matter most to you

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


Status Not under consideration
Workspace Spectrum LSF
Created by Guest
Created on May 9, 2016

Lock LSF daemon's memory pages to prevent swapping them out

As part of the discussion about the which NICE value should LSF daemon use, another idea to improve LSF resilience and consistency came up. See the PMR related.

LSF daemons should never send pages to swap. When this happens, and a fix pack replacing a daemon binary (like RES) is installed, it may happen that old RES instances from the running jobs crash when they are swapped back in. I think old daemon process tries to read some information from the binary which is not the same anymore so it crashes with a "bus error". If this is true, there is a potential problem for every single running job on the cluster when LSF is updated.

We have seen this problem in the past, but this is just a theory that we could not proof. Does it make any sense?

Of course, this may be implemented as an optional parameter.

Thanks.

  • Guest
    Reply
    |
    May 20, 2019

    While the described steps force RES to be swapped, and thus the error, we feel that this is very unlikely to happen in reality as RES is an active process and not likely to get swapped unless a system is critically low on memory.

  • Guest
    Reply
    |
    Nov 24, 2016

    With the Linux transition to systemd which uses cgroups by default, you may think of placing all the LSF daemons on a LSF service cgroup to guarantee certain amount of h/w resources for the service. If that would be the case, you could also configure swapiness to 0 to avoid (or mitigate) the daemons are swapped in/out.

    Of course, that would have to work in combination with the current cgroups integration and the fact that job's processes are children of a RES fork in a different cgroups path.

  • Guest
    Reply
    |
    May 10, 2016

    Creating a new RFE based on Community RFE #88010 in product Platform LSF.