Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: 每个 TiDB 集群都要部署一个 TiCDC 集群，有没有可能多个 TiDB 集群共用一个 TiCDC 集群
|
username: mxd-321
Since each TiDB cluster needs to deploy a TiCDC cluster, this consumes a lot of resources and makes it inconvenient to manage TiCDC tasks. Is it possible for multiple TiDB clusters to share a single TiCDC cluster, so that only one TiCDC cluster needs to be deployed?
It should not be possible for multiple TiDB clusters to share a single TiCDC cluster, but it can synchronize data to multiple downstreams.
TiCDC retrieves logs from TiKV, so it cannot be shared.
TiCDC, as an incremental data synchronization tool for TiDB, achieves high availability through the internal etcd of PD. It obtains data changes from TiKV nodes via multiple TiCDC processes, performs internal sorting, merging, and other processing, and then synchronizes data to multiple downstream systems simultaneously through multiple synchronization tasks (Changefeed).
TiCDC is not suitable. It can be deployed together with TiKV or TiDB as long as resource isolation is properly managed.
Thank you, boss. Is there a tool that can manage these TiCDC clusters?
Isn’t tiup itself directly managing it? Are you deploying it using binary now?
The requirements are being worked on, but the timeline is not guaranteed, you know. TiDB Roadmap | PingCAP Docs
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: