-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 description about ticdc new architecture #19765
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.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Co-authored-by: Flowyi <[email protected]>
@lidezhu: The following test 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-sigs/prow repository. I understand the commands that are listed here. |
|
||
TiCDC 新架构由两个主要部分组成,分别是 Log Service 和 Downstream Adapter,其中 Log Service 负责拉取上游集群的行变更和 DDL 信息并存储在本地,Downstream Adapter 则根据用户创建的 Changefeed 信息产生相关的同步任务从 Log Service 拉取相关数据并同步到下游。 | ||
|
||
### 核心组件 |
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.
建议不要把内部的模块写在用户文档上,因为这些东西用户并不关心,并且后续还有可能会改。可以考虑换成新架构的设计特点,可以考虑从这几个点:
- 描述将系统划分为 Log Service 和 Downstream Adapter 的原因和带来的好处
- Timer Drivent 和 Event Drivent 模型,提升并发度、执行效率和扩展能力,同时可以处理海量的表
- 代码结构优化,降低复杂度
config: | ||
newarch: true | ||
``` | ||
|
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.
NOTE: 在使用 TiCDC 老架构时,请勿在配置文件中添加 `newarch` 配置项。`newarch` 仅用于新架构,不添加 `newarch` 配置项默认使用老架构。如果在 TiCDC 老架构的配置文件中添加 newarch,可能会导致解析失败。 | |
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.
/CC @flowbehappy
@wlwilliamx: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this: 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-sigs/prow repository. |
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.
/CC @flowbehappy
### `newarch` | ||
|
||
- v9.0 版本引入,控制是否开启 TiCDC 新架构 | ||
- 默认值:`false`,表示不开启 TiCDC 新架构 |
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.
- 默认值:`false`,表示不开启 TiCDC 新架构 | |
- 设置为 `true`,表示开启 TiCDC 新架构 | |
- 不添加 `newarch` 配置项默认使用老架构。`newarch` 仅用于新架构,如果在 TiCDC 老架构的配置文件中添加 newarch,可能会导致解析失败。 |
@wlwilliamx: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this:
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-sigs/prow repository. |
First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?