Skip to content
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

Ensure there is at most a single pending authorization check per (uid, serviceName) pair at any given time. #10669

Open
mateusazis opened this issue Nov 15, 2023 · 0 comments

Comments

@mateusazis
Copy link
Contributor

TODO follow-up from this conversation.

#10566 introduced asynchronous authorization checks. Previously, when there were only synchronous policies, the number of concurrent checks was naturally limited by the number of threads in the fixed-size executor they ran on. Now, the system just spawns new checks as requests come, so this leads to an unbounded number of checks.

This issue is currently mitigated by the fact that most requests should use caching, but we should still improve it for the rest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants