-
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]>
@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
@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. |
Co-authored-by: wlwilliamx <[email protected]>
Co-authored-by: wlwilliamx <[email protected]>
…ocs-cn into ldz/add-ticdc-new-arch
|
||
1. 如果你的 TiDB 集群中尚无 TiCDC 节点,参考[扩容 TiCDC 节点](/scale-tidb-using-tiup.md#扩容-ticdc-节点)在集群中扩容新的 TiCDC 节点,否则跳过该步骤。 | ||
|
||
2. 如果你的 TiDB 集群为 v9.0.0 之前版本,需要按照以下方式手动下载 v9.0.0 或以上版本的 TiCDC 离线包,并将下载的 TiCDC 二进制文件 Patch 到你的 TiDB 集群,否则跳过该步骤。 |
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.
2. 如果你的 TiDB 集群为 v9.0.0 之前版本,需要按照以下方式手动下载 v9.0.0 或以上版本的 TiCDC 离线包,并将下载的 TiCDC 二进制文件 Patch 到你的 TiDB 集群,否则跳过该步骤。 | |
2. 如果你的 TiDB 集群为 v9.0.0 之前版本,需要按照以下方式手动下载 v9.0.0 或以上版本的 TiCDC 离线包,并将下载的 TiCDC 二进制文件动态替换到你的 TiDB 集群,否则跳过该步骤。 |
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.
@lidezhu, PTAL, thanks
wget https://tiup-mirrors.pingcap.com/cdc-v9.0.0-linux-amd64.tar.gz | ||
``` | ||
|
||
2. 将下载的 TiCDC 二进制文件 Patch 到你的 TiDB 集群中: |
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.
2. 将下载的 TiCDC 二进制文件 Patch 到你的 TiDB 集群中: | |
2. 使用 [`tiup cluster patch`](/tiup/tiup-component-cluster-patch.md) 命令将下载的 TiCDC 二进制文件动态替换到你的 TiDB 集群中: |
Co-authored-by: Aolin <[email protected]>
Co-authored-by: Aolin <[email protected]>
Co-authored-by: Aolin <[email protected]>
- **更高的单节点性能**:单节点最高可支持 50 万张表的同步任务,宽表场景下的同步流量最高可达 200 MiB/s。 | ||
- **更强的扩展能力**:集群同步能力接近线性扩展,单集群可扩展至超过 100 个节点,支持超 1 万个 Changefeed;单个 Changefeed 可支持百万级表的同步任务。 | ||
- **更高的稳定性**:在高流量、频繁 DDL 操作及集群扩缩容等场景下,Changefeed 的延迟更低且更加稳定。通过资源隔离和优先级调度,减少了多个 Changefeed 任务之间的相互干扰。 | ||
- **更低的资源成本**:通过改进资源利用率,减少冗余开销。在典型场景下,CPU 和内存等资源的利用效率提升高达一个数量级。 |
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.
"提升高达一个数量级"是指“提升 10 倍”吗
例如,可以使用以下命令下载 Linux 系统 x86-64 架构的 TiCDC v9.0.0 的二进制文件: | ||
|
||
```shell | ||
wget https://tiup-mirrors.pingcap.com/cdc-v9.0.0-linux-amd64.tar.gz |
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 link does not work for now. As this doc will be displayed only in the dev version, is it okay?
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?