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

Post comment

Guest

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

0 reply Hide replies

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.

Please enter your email address

RELATED IDEAS

LSF Complementations in Delaying LDAP Responses