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

Bug Report: vreplication and vitess online ddl lose rows_copied on reparent #13948

Closed
olyazavr opened this issue Sep 11, 2023 · 0 comments · Fixed by #13949
Closed

Bug Report: vreplication and vitess online ddl lose rows_copied on reparent #13948

olyazavr opened this issue Sep 11, 2023 · 0 comments · Fixed by #13949
Labels
Needs Triage This issue needs to be correctly labelled and triaged Type: Bug

Comments

@olyazavr
Copy link
Contributor

Overview of the Issue

Upon reparent (planned or not), we were seeing a loss of progress in migrations (eg. progress dropping from 90% to 0%). In diving deeper, I noticed that the underlying vreplication stream would continue along, as advertised, and the migration would actually complete, but at < 100% completion reported (however, the percentages before the reparent and after completion would add up to 100%, which pointed me in the right direction).

I found that the rows_copied counter was reset in vreplication upon reparent, but the actual position was kept correct, so this is more of a cosmetic issue, but alarming to see your whole migration drop to 0% on a reparent

Slack conversation

Reproduction Steps

Start a vitess onlineddl migration, wait until it has made some progress, and then reparent. Progress and rows copied will drop to 0, as they will in the underlying vreplication stream. However, the migration will successfully complete, BUT report that it has completed at less than 100% progress and rows_copied will not reach total row count

Binary Version

Vitess 14

Operating System and Environment details

Centos8, Linux 5.4.141-hs22.el8.x86_64

Log Fragments

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Triage This issue needs to be correctly labelled and triaged Type: Bug
Projects
None yet
1 participant