-
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
redo(ticdc): make implementation in manager asynchronously #5683
redo(ticdc): make implementation in manager asynchronously #5683
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. |
4c04494
to
fcc5d5d
Compare
02ed825
to
3c53e6a
Compare
Codecov Report
Flags with carried forward coverage won't be shown. Click here to find out more. @@ Coverage Diff @@
## master #5683 +/- ##
================================================
- Coverage 58.6479% 57.7402% -0.9078%
================================================
Files 711 701 -10
Lines 83933 82866 -1067
================================================
- Hits 49225 47847 -1378
- Misses 30258 30657 +399
+ Partials 4450 4362 -88 |
e36e1e9
to
b516897
Compare
5d9a9da
to
e5178fc
Compare
d07c5a6
to
7cf1624
Compare
76e110c
to
374d695
Compare
/run-all-tests |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 374d695
|
/run-all-tests |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 515377f
|
1 similar comment
This pull request has been accepted and is ready to merge. Commit hash: 515377f
|
/label needs-cherry-pick-release-6.1 |
/run-cherry-picker |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created: #6199. |
What problem does this PR solve?
Issue Number: close #6011, ref #5920
What is changed and how it works?
bgUpdateLog
to write and flush log to backend storage serially.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