我的书签
添加书签
移除书签TiCDC Deployment Topology
Note
TiCDC is a feature for general availability (GA) since v4.0.6. You can use it in the production environment.
This document describes the deployment topology of TiCDC based on the minimal cluster topology.
TiCDC is a tool for replicating the incremental data of TiDB, introduced in TiDB 4.0. It supports multiple downstream platforms, such as TiDB, MySQL, Kafka, MQ, and storage services. Compared with TiDB Binlog, TiCDC has lower latency and native high availability.
Topology information
| Instance | Count | Physical machine configuration | IP | Configuration |
|---|---|---|---|---|
| TiDB | 3 | 16 VCore 32GB 1 | 10.0.1.1 10.0.1.2 10.0.1.3 | Default port Global directory configuration |
| PD | 3 | 4 VCore 8GB 1 | 10.0.1.4 10.0.1.5 10.0.1.6 | Default port Global directory configuration |
| TiKV | 3 | 16 VCore 32GB 2TB (nvme ssd) 1 | 10.0.1.7 10.0.1.8 10.0.1.9 | Default port Global directory configuration |
| CDC | 3 | 8 VCore 16GB 1 | 10.0.1.11 10.0.1.12 10.0.1.13 | Default port Global directory configuration |
| Monitoring & Grafana | 1 | 4 VCore 8GB * 1 500GB (ssd) | 10.0.1.11 | Default port Global directory configuration |
Topology templates
For detailed descriptions of the configuration items in the above TiDB cluster topology file, see Topology Configuration File for Deploying TiDB Using TiUP.
Note
- You do not need to manually create the
tidbuser in the configuration file. The TiUP cluster component automatically creates thetidbuser on the target machines. You can customize the user, or keep the user consistent with the control machine. - If you configure the deployment directory as a relative path, the cluster will be deployed in the home directory of the user.
