You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
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?
The text was updated successfully, but these errors were encountered: