NFS Master-Slave Cluster Deployment

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

Original topic: nfs 主从集群部署

| username: TiDBer_sX3j5LdU

[TiDB Usage Environment] Production Environment
[TiDB Version] 6.1.3
[Reproduction Path] Operations performed that led to the issue
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]
Background: Deployed two clusters. Each cluster has three nodes. The underlying backup storage is NFS. The original plan was to perform a full backup once a day, and if one cluster fails, the other cluster would be started.
Requirement: Saw in the documentation that there is a dual-cluster master-slave replication mode, and want to upgrade to this mode.
Questions:

  1. Currently, neither cluster has the TiDC component. How to deploy it? Do both clusters need to add DC? How to add it dynamically?
  2. Does this mode support NFS incremental synchronization?
| username: tidb菜鸟一只 | Original post link

Are both clusters currently in use?
For example, is database a on cluster A providing services externally, and is database b on cluster B providing services externally?

| username: WalterWj | Original post link

TiCDC dual-master mode? Is this necessary?

| username: zhanggame1 | Original post link

To deploy, just refer to the official documentation:
TiCDC Overview | PingCAP Documentation Center

TiCDC is real-time synchronization with very low latency. It can be deployed on both the primary and standby databases. Your requirements can be seen in the screenshots:


| username: TiDBer_sX3j5LdU | Original post link

The A database provides external services, while the B database is positioned only as a backup cluster to be used when the A database is unavailable.

| username: TiDBer_sX3j5LdU | Original post link

I already have a deployed cluster, how do I add TiCDC?

| username: ShawnYan | Original post link

If you can upgrade the version, you can use TiKV CDC.

| username: tidb菜鸟一只 | Original post link

That’s very simple. Just expand the ticdc nodes in cluster A, then deploy the task to synchronize changes from database A to cluster B. Refer to the following steps:

| username: TiDBer_sX3j5LdU | Original post link

Thank you, much appreciated.

| username: TiDBer_sX3j5LdU | Original post link

Thank you, it has been resolved.

| username: TiDBer_sX3j5LdU | Original post link

6.1.3 can also be used.

| username: ShawnYan | Original post link

TiKV CDC can only be used in version 6.2.0 and above.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.