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
As we know, badmin reconfig checks whether an invalid user is set in lsb.users.
But if an LDAP response is very delayed, LSF can only continue to wait for this.
LSF does not have a function to reduce the username resolution time, and LSF does not logic to ignore username resolution.
I understand up to this point.
However, the LDAP environment cannot always be good.
And if an LDAP response is very delayed, while the main process of mbatchd is busy in doing above things, some b command, like bsub, may not be responded.
This will affect the bsub until the username resolution is complete.
So I hope it will create a function that can supplement this.
For example, if an LDAP response is very delayed, I want to ignore the username resolution.
I think there could be a problem when we skip "checking invalid user" this process.
As a result, I hope for the two logic below.
1. Logic to skip username resolution only in certain cases(For example, when an LDAP response is very delayed)
2. Logic to minimize problems caused by skipping
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.
If you are using parallel restart, then the checking of usernames is done in a completely separate process from the production mbatchd.
If ldap is slow in responding, then usernames won't be resolved at dispatch and jobs will fail.
The warning during reconfig is exactly that, a warning that there are environment issues with resolving usernames.