-
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
processor(ticdc): Fix processor panic issue #10922
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 3AceShowHand, asddongmen The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
Codecov Report
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. @@ Coverage Diff @@
## master #10922 +/- ##
================================================
+ Coverage 57.3986% 57.4272% +0.0285%
================================================
Files 850 850
Lines 125137 125141 +4
================================================
+ Hits 71827 71865 +38
+ Misses 47914 47883 -31
+ Partials 5396 5393 -3 |
/retest-required |
1 similar comment
/retest-required |
/retest |
/retest-required |
What problem does this PR solve?
Issue Number: close #10921
What is changed and how it works?
If a processor is not initialized and then call writerDebugInfo command, ticdc will panic because of tableManager is nil
this PR will check if the processor is initialized or not, if not initialized, then print a log, false add a ut case to cover it.
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