-
Notifications
You must be signed in to change notification settings - Fork 298
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
[BUG] Tenant Calculation(?) quite expensive #5129
Comments
Have the performance issues been present since the first time you have used OpenSearch, or was it a regression at some point? Do you have figures regarding the slowdown comparing your custom plugin and the performance observed with OpenSearch 2.19? |
Hi, maybe I opened the issue too early. Sorry for disturbance. We optimized the role assigned to our bulk index user to not have tenant_permissions '*' . This omits the mapTenants call as the user has no access to any tenant. Your optimizations work quite fine - thanks a lot for this! I'm unsure if this issue should stay open, as a user with tenant_permissions '*' in a environment with many tenants till has a slow(er) permission check or if we should close this as inperformant configuration for a bulk index user. best regards and thanks again! |
No worries, I do think that the hot thread dump indicates an issue. However, at the moment I believe it is a separate issue. That's why I am curious about the actual impact and whether it was a regression at some point. |
@HenryTheSir FYI 2.19 has a separate optimization for all_access as well using the legacy authz code path: #4926 |
@HenryTheSir thank you for filing this issue. It sounds like possibly optimizing the privileges evaluation flow has uncovered other issues in terms of tenancy calculations. Someone will take a look. |
What is the bug?
After Upgrading from 2.18 to 2.19 we tried to drop our custom build security plugin which would return true as soon as it could determine that a user has all_access.
I'm currently unsure if this is a bottleneck of the optimized priviledge evaluation or a different root cause which occurs as we have arround 250 Tenants.
How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
In a write requests tenants should not be evaluated.
The text was updated successfully, but these errors were encountered: