Experts, can you tell me what the standard CDC deployment architecture for TiDB 6.5.0 is like? If deploying on a single machine in a test environment, what should I pay attention to?

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 大佬们 问一下tidb6.5.0 标准的cdc部署架构是怎么样。如果是实验环境单机部署需要注意些什么

| username: tidb狂热爱好者

[TiDB Usage Environment] Production Environment 6.5
[Reproduction Path] What operations were performed when the problem occurred
I am sending the configuration list
global:
user: “tidb”
ssh_port: 22
deploy_dir: “/tidb-deploy”
data_dir: “/home/tidb-data”

pd_servers:

  • host: 172.21.10.147

tidb_servers:

  • host: 172.21.10.147

tikv_servers:

  • host: 172.21.10.147

cdc_servers:

  • host: 172.21.10.147

monitoring_servers:

  • host: 172.21.10.147

grafana_servers:

  • host: 172.21.10.147

alertmanager_servers:

  • host: 172.21.10.147
    [Encountered Problem: Problem Phenomenon and Impact]
    [Resource Configuration]
    [Attachment: Screenshot/Log/Monitoring]
| username: WalterWj | Original post link

It’s just a single-machine deployment for testing, so isn’t it fine to do it casually?

| username: tidb狂热爱好者 | Original post link

What I need is the standard deployment method. If it’s a single machine, I hope your company can provide a rate limiting template.

| username: Lucien-卢西恩 | Original post link

Sorry, for single-node deployment scenarios, it is mainly necessary to use Cgroup or NUMA tools to limit and isolate system resources for PD, TiKV, TiDB, and TiCDC services to avoid unnecessary resource contention. However, single-node clusters are only for functional testing, and it is strongly recommended to use TiUP Playground to experience TiDB features.