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

Cluster (i.e. first pod) start must be managed manually #6

Open
solsson opened this issue Sep 7, 2017 · 0 comments
Open

Cluster (i.e. first pod) start must be managed manually #6

solsson opened this issue Sep 7, 2017 · 0 comments

Comments

@solsson
Copy link
Contributor

solsson commented Sep 7, 2017

See https://github.com/Yolean/kubernetes-mysql-cluster#initialize-volumes-and-cluster for background.

The manual toggle of --wsrep-new-cluster is particularly bad if you suffer unplanned downtime. The cluster will not initialize, or worse you'll get replicas but they are disconnected, without manual intervention.

Someone told me there is a mechanism for running a special type of init container for the first pod in a replica set. Can't find it now.

@Jacobh2 we should look into this if you plan on running multiple clusters/instances. You might start a single instance per site, but with the possibility to scale up individual sites as load increase.

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

No branches or pull requests

1 participant