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

Vertical scaling support #906

Open
AntonAleksandrov13 opened this issue Nov 21, 2024 · 2 comments · May be fixed by #912
Open

Vertical scaling support #906

AntonAleksandrov13 opened this issue Nov 21, 2024 · 2 comments · May be fixed by #912

Comments

@AntonAleksandrov13
Copy link

Is your feature request related to a problem? Please describe.
We are managing a large amount of objects with messaging-topology-operator(75k+), when operator restarts due to update/eviction/others reason, reconciliation of all objects takes about 30+ minutes. During this time, it is highly likely that we would want to add a new object. This means that the worst case scenario a reconciliation of a new object could take 30+ minutes. This is critical for us as this creates a bottleneck in the system where other applications have to wait.

It seems like MaxConcurrentReconciles is not set in the operator which means that every controller can perform 1 operation at the time.

Describe the solution you'd like
I would like to see configurable MaxConcurrentReconciles value using env variables.

Describe alternatives you've considered
I have tried horizontally scale the operator, but the second replica does nothing. As a workaround, I have considered using ControllerMesh(https://blog.kusionstack.io/controllermesh-empowering-effortless-operator-management-2f57b6203719), but this seems too hacky and might not be an option to the most users.

@Zerpet
Copy link
Contributor

Zerpet commented Nov 25, 2024

This sounds reasonable. I don't have time to work on this immediately, but I'll be happy to review a contribution.

@AntonAleksandrov13
Copy link
Author

No worries. I can work on it

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