-
Notifications
You must be signed in to change notification settings - Fork 288
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
dm: revert dm#2047 #3491
dm: revert dm#2047 #3491
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/run-all-tests |
/run-kafka-integration-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
the difference of this revert PR and dm#2048 is https://github.com/pingcap/dm/pull/2047/files#diff-e725a03bd475dc4ea28028613ede1fd88a8cc8f881f0a1788a189e766f191830R1869
after this PR, we reset streamer to s.checkpoint.GlobalPoint()
but before dm#2048, we reset streamer to lastLocation
.
s.checkpoint.GlobalPoint()
is updated in three places: xid job, ddl job, handle-error skip. In the first two places lastLocation
is equal to s.checkpoint.GlobalPoint()
. In the last place s.checkpoint.GlobalPoint()
is forwarded, I think it's better than lastLocation
because we now remember user's action after ResetReplicationSyncer
/run-dm-integration-test |
rest LGTM
One situation is sequence sharding ddl, lastLocation is forwarded but global checkpoint is not, may this cause some problem? 🤔 |
/run-dm-integration-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/run-all-tests |
We may also update |
/run-all-tests |
/run-all-tests |
/run-kafka-integration-test |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 285c0e2
|
/run-integration-test |
What problem does this PR solve?
Revert dm#2047 due to #3487
Also cherry-pick #3413 #3435 #3471 to make integration stable.
What is changed and how it works?
Check List
Tests
Code changes
Side effects
Related changes
Release note