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:

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:

Status Delivered
Workspace Spectrum LSF
Created by Guest
Created on Jul 6, 2021

LSF Complementations in Delaying LDAP Responses

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

  • Guest
    Jul 23, 2021

    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.