-
Notifications
You must be signed in to change notification settings - Fork 289
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): use uuid in redo meta filename (#8075) #8130
redo(ticdc): use uuid in redo meta filename (#8075) #8130
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. |
Codecov Report
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. @@ Coverage Diff @@
## release-6.5 #8130 +/- ##
================================================
Coverage ? 62.7726%
================================================
Files ? 918
Lines ? 123796
Branches ? 0
================================================
Hits ? 77710
Misses ? 40099
Partials ? 5987 |
/run-all-tests |
/run-verify |
a4d2ce2
to
8247ec4
Compare
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 8247ec4
|
@ti-chi-bot: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests
If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. Instructions 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 ti-community-infra/tichi repository. |
/run-verify |
This is an automated cherry-pick of #8075
What problem does this PR solve?
Issue Number: close #8074, close #8028
What is changed and how it works?
Use uuid in redo meta filename to avoid frequent access to the same object.
Add metricRedoWorkerBusyRatio to redoManager.
![image](https://user-images.githubusercontent.com/61726649/213391713-2ced7f05-be4a-4083-a751-6072ee69044a.png)
Fix the limit on flush-interval.
Add test.Dockerfile facilitate testing.
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