-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Since RELEASE.2024-03-26T22-10-45Z console UI is very slow for LDAP authenticated users. #19746
Comments
@bexsoft we have a community report now for the same issue. |
Hello! We have the same issue. We noticed that the more groups a user has, the slower the console opens. The "mcli ls" command with access keys is also slower. |
@abisek9186-baloise we haven't been able to reproduce this with any baremetal setups. |
@harshavardhana thanks for the update. I reported this particular issue on MinIO operator managed MinIO tenants on OpenShift. |
Yeah tried k8s yesterday nothing yet. it looks like we are missing something else here. Is your LDAP an AD server or OpenLDAP ? |
We are using AD and six nodes linux cluster. How could we grub diagnostic info for this issue? |
Console UI is really slow (takes around 20 to 30 seconds to load the object browser). We have around 150 objects across 3 buckets in this minio instance so number of objects should not be an issue.
Expected Behavior
Console UI should list the objects as fast as root user based login does.
While browsing via root login, the browsing is very fast, and akes ~1-2 secs only to load the object browser.
Current Behavior
Consule UI is realluy slow (takes around 20 to 30 seconds to load the object browser).
Performance for mc CLI against the MinIO API is consistently fast.
Current env variable which sets the LDAP config for the tenant, is below:
value: "ou=Users,ou=XXX,dc=YYY,dc=com"
value: "(&(objectCategory=person)(sAMAccountName=%s))"
value: "ou=Ressources-GRP,ou=Groups,ou=XXX,dc=YYY,dc=com"
value: "(&(objectClass=group)(member=%d))"
Your Environment
minio --version
): Any release after RELEASE.2024-03-26T22-10-45Z behaves the sameuname -a
): OCP 4.14The text was updated successfully, but these errors were encountered: