-
Notifications
You must be signed in to change notification settings - Fork 286
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
cdc: region worker should handle stale events correctly (#9078) #9081
cdc: region worker should handle stale events correctly (#9078) #9081
Conversation
[REVIEW NOTIFICATION] This pull request has not been approved. 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. |
Signed-off-by: qupeng <qupeng@pingcap.com> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
65950df
to
0eb8d82
Compare
close pingcap#9072 Signed-off-by: qupeng <qupeng@pingcap.com>
0eb8d82
to
8258169
Compare
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 8258169
|
Signed-off-by: qupeng <qupeng@pingcap.com>
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 23bfb85
|
This is an automated cherry-pick of #9078
What problem does this PR solve?
Issue Number: close #9072
What is changed and how it works?
Region worker should handle stale events correctly.
Check List
Tests
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note