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


Add a new idea Subscribe
Status Delivered
Workspace Spectrum LSF
Created by Guest
Created on Nov 2, 2016

RELATED IDEAS

LSF is not starting correctly with LDAP duing node boots

Every time we reboot nodes LSF jobs will switch from RUN to PEND status. We have found knowledge base document that states using LDAP with LSF is a known issue.

https://www.ibm.com/support/knowledgecenter/SSENRW_4.2.1/release_notes/known_issues.html

The workaround for this Known Issue is to Kill the jobs and restart LSF daemon on the node.

As a result of this Known Issue the jobs that were looping cause the event.lsb file to grow. we had approximate 3000 jobs but our event.lsb file was over 400MB is size. This caused the bhist command performance to take minutes to return output.

Can you please document the cause of the Known Issue? We have found if LSF starts before LDAP on the node this situation is 100% reproducible. If LSF needs to be started after LDAP it seems that you have a bug that requires to be fixed rather then an enhancement.

The solution of killing jobs and restarting daemon will not be acceptable to CORAL customers. We are only testing on 18 nodes, they will be using 2500 nodes. The documentation seems to be written for smaller clusters. It only describes how to get out of the looping but does not describe how to avoid the looping by configuring the node correctly.

  • Guest
    Reply
    |     Dec 22, 2016

    The known issue you point to is nothing to do with the LSF core.
    If the system is using LDAP, then it must be started before LSF - otherwise LSF will not be able to resolve the users.
    Starting LSF after LDAP, NIS, etc is the usual boot order.

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.