-
Notifications
You must be signed in to change notification settings - Fork 33
sink: retry later when meet unexpected DDL state #3948
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
base: master
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Summary of ChangesHello @wk989898, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly improves the resilience of the CDC sink by enhancing its DDL error handling mechanism. By marking Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
|
[FORMAT CHECKER NOTIFICATION] Notice: To remove the 📖 For more info, you can check the "Contribute Code" section in the development guide. |
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.
Code Review
This pull request correctly makes ErrDDLStateNotFound a retryable error, which will prevent changefeed restarts when encountering slow DDLs. The core logic change is simple and is well-supported by a new test file that improves coverage for error-handling utilities. The pull request also includes some nice refactorings, such as using a more specific error type and updating a log message to reflect the new retry behavior. My review includes a couple of suggestions to improve the quality and readability of the new test cases by using more accurate error messages.
| {newMysqlErr(tmysql.ErrNoDB, "Error: Duplicate key name 'some_key'"), false}, | ||
| {newMysqlErr(tmysql.ErrParse, "Can't create database"), false}, | ||
| {newMysqlErr(tmysql.ErrAccessDenied, "Access denied for user"), false}, | ||
| {newMysqlErr(tmysql.ErrDBaccessDenied, "Access denied for db"), false}, | ||
| {newMysqlErr(tmysql.ErrNoSuchTable, "table not exist"), false}, | ||
| {newMysqlErr(tmysql.ErrNoSuchIndex, "index not exist"), false}, | ||
| {newMysqlErr(tmysql.ErrWrongColumnName, "wrong column name'"), false}, | ||
| {newMysqlErr(tmysql.ErrDupKeyName, "Duplicate key name 'some_key'"), true}, | ||
| {newMysqlErr(tmysql.ErrPartitionMgmtOnNonpartitioned, "xx"), false}, | ||
| {newMysqlErr(tmysql.ErrNonuniqTable, "xx"), false}, | ||
| {newMysqlErr(tmysql.ErrBadDB, "xx"), false}, |
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.
The error messages for several test cases in TestIsRetryableDDLError seem to be either placeholders ("xx") or potentially incorrect due to copy-pasting. For example, on line 100, tmysql.ErrNoDB is paired with a message for a duplicate key error.
For better test clarity and correctness, please review and update these messages to be representative of the actual errors being tested. This will make the tests more robust and easier to understand.
| {newMysqlErr(tmysql.ErrDupKeyName, "Error: Duplicate key name 'some_key'"), false}, | ||
| {newMysqlErr(tmysql.ErrNoDB, "Error: Duplicate key name 'some_key'"), false}, | ||
| {newMysqlErr(tmysql.ErrParse, "Can't create database"), false}, |
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.
The error messages for these test cases appear to be incorrect, likely due to copy-pasting. For instance, tmysql.ErrNoDB is associated with a 'Duplicate key name' message. To improve test clarity and correctness, please ensure the error messages accurately correspond to the error codes being tested.
|
@wk989898: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
| return true | ||
| } | ||
|
|
||
| if Is(err, ErrDDLStateNotFound) { |
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.
Does this error only occur in waitDDLDone queries? If so, it would be better to handle this function directly rather than broadening the scope of the error check.
Actually,I‘m not sure whether this error is return only by getDDLStateFromTiDB, and when will this error really happens?
What problem does this PR solve?
Issue Number: ref pingcap/tiflow#12482
What is changed and how it works?
When meeting the unexpected DDL state, instead of immediately failing, CDC now attempts to retry the DDL. This change aims to avoid CDC restart.
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