From e29d7b6d3dd113f8939cfa862eddae6c80c0e85f Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Tue, 9 Apr 2024 15:48:22 +0800 Subject: [PATCH 1/2] br: not support executing backup task and restore task at the same time (#17076) --- br/backup-and-restore-overview.md | 1 + 1 file changed, 1 insertion(+) diff --git a/br/backup-and-restore-overview.md b/br/backup-and-restore-overview.md index fb9b040e84706..5e1b4d7cb5e92 100644 --- a/br/backup-and-restore-overview.md +++ b/br/backup-and-restore-overview.md @@ -25,6 +25,7 @@ This section describes the prerequisites for using TiDB backup and restore, incl - PITR only supports cluster-level restore and does not support database-level or table-level restore. - PITR does not support restoring the data of user tables or privilege tables from system tables. - BR does not support running multiple backup tasks on a cluster **at the same time**. +- BR does not support running snapshot backup tasks and data restore tasks on a cluster **at the same time**. - When a PITR is running, you cannot run a log backup task or use TiCDC to replicate data to a downstream cluster. ### Some tips From dabf164312f69e093f54a31971106c07d8febd1c Mon Sep 17 00:00:00 2001 From: disksing Date: Wed, 10 Apr 2024 10:16:52 +0800 Subject: [PATCH 2/2] dr-autosync: add configuration description (#17057) --- two-data-centers-in-one-city-deployment.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/two-data-centers-in-one-city-deployment.md b/two-data-centers-in-one-city-deployment.md index 2a473d5303f9d..1c6d71fc5df6e 100644 --- a/two-data-centers-in-one-city-deployment.md +++ b/two-data-centers-in-one-city-deployment.md @@ -221,6 +221,7 @@ The replication mode is controlled by PD. You can configure the replication mode primary-replicas = 3 dr-replicas = 2 wait-store-timeout = "1m" + pause-region-split = false ``` - Method 2: If you have deployed a cluster, use pd-ctl commands to modify the configurations of PD. @@ -241,8 +242,9 @@ Descriptions of configuration items: + `replication-mode` is the replication mode to be enabled. In the preceding example, it is set to `dr-auto-sync`. By default, the majority protocol is used. + `label-key` is used to distinguish different AZs and needs to match Placement Rules. In this example, the primary AZ is "east" and the disaster recovery AZ is "west". + `primary-replicas` is the number of Voter replicas in the primary AZ. -+ `dr-replicas` is the number of Voter replicas in the disaster recovery AZ. ++ `dr-replicas` is the number of Voter replicas in the disaster recovery (DR) AZ. + `wait-store-timeout` is the waiting time for switching to asynchronous replication mode when network isolation or failure occurs. If the time of network failure exceeds the waiting time, asynchronous replication mode is enabled. The default waiting time is 60 seconds. ++ `pause-region-split` controls whether to pause Region split operations in the `async_wait` and `async` statuses. Pausing Region split can prevent temporary partial data loss in the DR AZ when synchronizing data in the `sync-recover` status. The default value is `false`. To check the current replication status of the cluster, use the following API: