IBM Data and AI Ideas Portal for Customers


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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Delivered
Workspace Spectrum LSF
Created by Guest
Created on Dec 16, 2014

LSF enforced limits

LSF currently inherits the environment (limits) from the system when the LSF Daemons are started, and doesn't compensate based on whether the LSF daemons are started by process 1 (init) or by root.
If LSF is configured to startup as part of the system boot process, the LSF daemons are started by the init process and changes that are configures in /etc/security/limits.conf, e.g. Max Locked Memory, are not applicable. However, if the LSF daemons are started on a system that is already running, the configured parameters in /etc/security/limits.conf are applicable.
The default "Max Locked Memory" on a RHEL 6.4 system is 64K.
If the system is configured to change the defaults "Max Locked Memory" to unlimited, LSF will behave differently depending on how LSF was started on the LSF Servers.

The request is for LSF to provide a mechanism where the limits enforced by LSF are consistent whether LSF is started by the init process or started by root.
Current work around is to customize /etc/init.d/lsf to change the hard and soft "Max Locked Memory" limit to match the setting in / etc/security/limits.conf. The work-around is challenging from a maintenance point of view, and in particular during system upgrades.

  • Guest
    Mar 26, 2015

    Hi Bhavin,

    The feature USE_PAM_CREDS may resolve your concern.

    - When this feature is enabled, LSF will use the PAM API to set the limits defined in /etc/security/limits.conf.
    - One limitation is that the feature doesn't work for jobs launched from blaunch.
    - USE_PAM_CREDS is a queue and application profile parameter.
    - Documentation is found in the lsb.queues and lsb.applications sections of the configuration reference. The lsb.queues reference for LSF 9.1.3 can be viewed online at the URL: https://www-01.ibm.com/support/knowledgecenter/SSETD4_9.1.3/lsf_config_ref/lsb.queues.5.dita
    - The feature was added in LSF 7.0.3.
    - PAM must be configured before the feature will work. To configure PAM, create a file (/etc/pam.d/lsf) and add the following lines to the file.

    auth required pam_localuser.so
    account required pam_unix.so
    session required pam_limits.so

  • Guest
    Jan 14, 2015

    This is not an LSF behaviour, but a standard linux kernel behaviour. No process started by init.d reads /etc/security/limit.conf. /etc/security/limits.conf is only read by pam interactive sessions.

    Blindly unlimited max locked memory may not be the desirable option in all clusters.

    We willl look at this in more detail in a future release.

  • Guest
    Dec 18, 2014

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