-
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
(ticdc) add cdc engineering and architecture roadmap #10498
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: zhangjinpeng87 <[email protected]>
Signed-off-by: zhangjinpeng87 <[email protected]>
Signed-off-by: zhangjinpeng87 <[email protected]>
[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.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: zhangjinpeng87 <[email protected]>
Signed-off-by: zhangjinpeng87 <[email protected]>
Signed-off-by: zhangjinpeng87 <[email protected]>
Signed-off-by: zhangjinpeng87 <[email protected]>
@zhangjinpeng87: The following tests failed, say
Full PR test history. Your PR dashboard. 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 kubernetes/test-infra repository. I understand the commands that are listed here. |
### Goals | ||
|
||
- The replication lag is expected under planned operations like rolling restart, scale-in and scale-out TiCDC cluster, etc. | ||
- TiCDC can recover quickly under unexpected sinle node failure, partial network failure, and other temporary partial infra failtures. |
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.
- TiCDC can recover quickly under unexpected sinle node failure, partial network failure, and other temporary partial infra failtures. | |
- TiCDC can quickly recover from unexpected single node failures, partial network failures, and other temporary partial infrastructure failures. |
|
||
### Projects | ||
|
||
- TiCDC HA capability assesment |
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.
- TiCDC HA capability assesment | |
- TiCDC HA capability assessment |
### Projects | ||
|
||
- Remove upstream PD denpendency, store changefeed metadata to meta store | ||
- Throuput threshold for different upstream TiDB Cluster |
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.
Throupt -> throughput
|
||
- Remove upstream PD denpendency, store changefeed metadata to meta store | ||
- Throuput threshold for different upstream TiDB Cluster | ||
- TiCDC fetch data change logs from the Unified Log Service to eliminate incremental scan issue and simplify network complexity on cloud enviornment |
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.
- TiCDC fetch data change logs from the Unified Log Service to eliminate incremental scan issue and simplify network complexity on cloud enviornment | |
- TiCDC fetches data change logs from the Unified Log Service to eliminate incremental scan issue and simplify network complexity on cloud environment. |
|
||
- Remove upstream PD denpendency, store changefeed metadata to meta store | ||
- Throuput threshold for different upstream TiDB Cluster | ||
- TiCDC fetch data change logs from the Unified Log Service to eliminate incremental scan issue and simplify network complexity on cloud enviornment |
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.
This can also make the memory consumption of TiCDC server predictable.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. @@ Coverage Diff @@
## master #10498 +/- ##
================================================
- Coverage 57.3983% 53.9444% -3.4539%
================================================
Files 849 403 -446
Lines 125866 63519 -62347
================================================
- Hits 72245 34265 -37980
+ Misses 48209 26556 -21653
+ Partials 5412 2698 -2714 |
What problem does this PR solve?
Issue Number: close #10497
What is changed and how it works?
Add an open roadmap from the engineering and architecture aspects, to express our intension on this open source project in next 1~2 years.
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