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

Do gracefull master promotion when scaling down #217

Closed
AMecea opened this issue Jan 28, 2019 · 1 comment
Closed

Do gracefull master promotion when scaling down #217

AMecea opened this issue Jan 28, 2019 · 1 comment
Milestone
0.2.x

Comments

@AMecea
Copy link
Contributor

AMecea commented Jan 28, 2019 •
edited
Loading

Now there is a case when node-1 is master and node-0 is slave. During scaling down the cluster, node-1 will be killed during the process, then node-0 will be promoted. This action may end with data loss.

Will be better, before scaling down, to promote the replica that remains alive as master.
@AMecea AMecea added this to the 0.2.x milestone Jan 28, 2019
@calind
Copy link
Member

calind commented Feb 1, 2019

Duplicate of #15.

@calind calind closed this as completed Feb 1, 2019
chapsuk pushed a commit to chapsuk/mysql-operator that referenced this issue Oct 16, 2023
@aquarapid
Move relaxing consistency for vtbackup to a separate my.cnf file, (bi…
f5e5b86 
…tpoke#217)

applied after any vttablet customizations, which might enable
those consistency settings again in common configs.

Signed-off-by: Jacques Grove <aquarapid@gmail.com>
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.x
Development

No branches or pull requests
2 participants
@calind @AMecea