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.

Sign up for GitHub

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

Jump to bottom

Let the operator set the master writable #199

Closed
calind opened this issue Jan 14, 2019 · 0 comments · Fixed by #222
Closed

Let the operator set the master writable #199

calind opened this issue Jan 14, 2019 · 0 comments · Fixed by #222
Milestone
0.2.4

Comments

@calind
Copy link
Member

calind commented Jan 14, 2019

Currently the operator expects that orchestrator is configured with ApplyMySQLPromotionAfterMasterFailover=true. Instead we should let the operator decide which node is writable on its own and let orchestrator only change the topology.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.2.4
Development

Successfully merging a pull request may close this issue.

Let operator set master writable and set cluster ready only when it's healty bitpoke/mysql-operator
2 participants
@calind @AMecea