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

FEATURE: Operator primary vttablet balancer #544

Open
GenLN opened this issue Mar 28, 2024 · 1 comment
Open

FEATURE: Operator primary vttablet balancer #544

GenLN opened this issue Mar 28, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@GenLN
Copy link

GenLN commented Mar 28, 2024

Hi, does Vitess operator offer some kind of balancing/rebalancing primary vttablet deployment? Something like anti-affinty for pods etc..

To minimize the chance of the high-severity failures:
Primaries should be evenly assigned across Kubernetes nodes
Primaries should be evenly assigned across availability zones

More about custom solution using OR Tools found on this blog

If there isn't any solution for this offered by operator, is there any chance this could be available sometime soon?

@mattlord
Copy link
Contributor

mattlord commented Apr 2, 2024

hi @GenLN,

I don't think this will be available anytime soon, unfortunately. It would be a nice addition though! The vitess maintainers, of which there are not many, do all of the work related to vitess and the vitesss-operator: product/program/project management, engineering, documentation, community support, devrel, builds, releases, etc — in addition to each of us working for a large shop that runs Vitess and all the work that goes with supporting that internally. It's a lot, and we'd love to see new contributors! Are you interested in working on this?

@mattlord mattlord added the enhancement New feature or request label Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants