-
Notifications
You must be signed in to change notification settings - Fork 64
[perf] MCAD constantly throttled #434
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
Comments
Agree, we need to remove unused controllers in MCAD, here is a PR that we can revive: #277 |
@astefanutti MCAD from the main branch has some remediations around this problem, can you recommend what more could be improved? |
@asm582 these messages seem to be caused by an excessive usage of the discovery API, which are being client-side throttle, despite the QPS and maximum burst limits have already been increased. We could speculatively close this, given the large refactoring that has happened lately, but a quick search in the code points to the My suggestion would be to look at it more closely, and consider putting some caching or rate limiting mechanisms in place, for consuming the discovery API. |
When looking at the MCAD logs, I see that it is constantly being throttled, and it seems to be requesting all the CRDs available in the cluster:
this cannot be a good thing for performance.
The text was updated successfully, but these errors were encountered: