-
Notifications
You must be signed in to change notification settings - Fork 282
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
fb/latency(cdc): agent fix inconsistent state by tolerant duplicate messages. #5791
fb/latency(cdc): agent fix inconsistent state by tolerant duplicate messages. #5791
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. |
…essages. (pingcap#5791) * agent should return absent directly. * do not panic when remove table not exist. * no need to check for table status.
…essages. (pingcap#5791) * agent should return absent directly. * do not panic when remove table not exist. * no need to check for table status.
…essages. (pingcap#5791) * agent should return absent directly. * do not panic when remove table not exist. * no need to check for table status.
…essages. (pingcap#5791) * agent should return absent directly. * do not panic when remove table not exist. * no need to check for table status.
…essages. (pingcap#5791) * agent should return absent directly. * do not panic when remove table not exist. * no need to check for table status.
…essages. (pingcap#5791) * agent should return absent directly. * do not panic when remove table not exist. * no need to check for table status.
…essages. (pingcap#5791) * agent should return absent directly. * do not panic when remove table not exist. * no need to check for table status.
…essages. (pingcap#5791) * agent should return absent directly. * do not panic when remove table not exist. * no need to check for table status.
…essages. (#5791) * agent should return absent directly. * do not panic when remove table not exist. * no need to check for table status.
What problem does this PR solve?
Issue Number: ref #4757
What is changed and how it works?
for remove table request, check if the target exist before process the request.
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