Merge branch 'release-7.5' into patch-7

Oreoxmt · Oreoxmt · commit cda19ce822fa · 2024-04-02T11:48:05.000+08:00
diff --git a/TOC-tidb-cloud.md b/TOC-tidb-cloud.md
@@ -666,6 +666,8 @@
   - [2021](/tidb-cloud/release-notes-2021.md)
   - [2020](/tidb-cloud/release-notes-2020.md)
 - Maintenance Notification
+  - [[2024-04-18] TiDB Cloud Data Migration (DM) Feature Maintenance Notification](/tidb-cloud/notification-2024-04-18-dm-feature-maintenance.md)
+  - [[2024-04-11] TiDB Cloud Data Migration (DM) Feature Maintenance Notification](/tidb-cloud/notification-2024-04-11-dm-feature-maintenance.md)
   - [[2023-11-14] TiDB Dedicated Scale Feature Maintenance Notification](/tidb-cloud/notification-2023-11-14-scale-feature-maintenance.md)
   - [[2023-09-26] TiDB Cloud Console Maintenance Notification](/tidb-cloud/notification-2023-09-26-console-maintenance.md)
   - [[2023-08-31] TiDB Cloud Console Maintenance Notification](/tidb-cloud/notification-2023-08-31-console-maintenance.md)
diff --git a/sql-prepared-plan-cache.md b/sql-prepared-plan-cache.md
@@ -5,6 +5,13 @@ summary: Learn about SQL Prepared Execution Plan Cache in TiDB.
 
 # SQL Prepared Execution Plan Cache
 
+> **Warning:**
+>
+> If a cached `UPDATE` or `DELETE` statement encounters a DDL operation that modifies the relevant schema during execution, it might cause data inconsistency between tables and indexes. For more information, see [Issue #51407](https://github.com/pingcap/tidb/issues/51407). It is recommended to monitor the status of this issue and upgrade to [the latest LTS version](https://docs.pingcap.com/tidb/stable) to resolve this issue. Before upgrading, you can try the following workarounds:
+> 
+> - Before executing DDL, temporarily [disable the prepared plan cache](/system-variables.md#tidb_enable_prepared_plan_cache-new-in-v610), and re-enable it after the DDL is complete.
+> - Avoid executing DDL during business peak hours. After executing DDL, immediately run [`ADMIN CHECK TABLE`](/sql-statements/sql-statement-admin-check-table-index.md) to check the consistency between tables and indexes. If errors are found, rebuild the relevant indexes.
+
 TiDB supports execution plan caching for `Prepare` and `Execute` queries. This includes both forms of prepared statements:
 
 - Using the `COM_STMT_PREPARE` and `COM_STMT_EXECUTE` protocol features.
diff --git a/ticdc/ticdc-open-api-v2.md b/ticdc/ticdc-open-api-v2.md
@@ -356,11 +356,11 @@ The `sink.csv` parameters are described as follows:
 | `quote`                  | `STRING` type. The quotation character used to surround fields in the CSV file. If the value is empty, no quotation is used. The default value is `"`. |
 | `binary_encoding_method` | `STRING` type. The encoding method of binary data, which can be `"base64"` or `"hex"`. The default value is `"base64"`. |
 
-`sink.dispatchers`: for the sink of MQ type, you can use this parameter to configure the event dispatcher. The following dispatchers are supported: `default`, `ts`, `rowid`, and `table`. The dispatcher rules are as follows:
+`sink.dispatchers`: for the sink of MQ type, you can use this parameter to configure the event dispatcher. The following dispatchers are supported: `default`, `ts`, `index-value`, and `table`. The dispatcher rules are as follows:
 
 - `default`: dispatches events in the `table` mode.
 - `ts`: uses the commitTs of the row change to create the hash value and dispatch events.
-- `rowid`: uses the name and value of the selected HandleKey column to create the hash value and dispatch events.
+- `index-value`: uses the name and value of the selected HandleKey column to create the hash value and dispatch events.
 - `table`: uses the schema name of the table and the table name to create the hash value and dispatch events.
 
 `sink.dispatchers` is an array. The parameters are described as follows:
diff --git a/ticdc/ticdc-open-api.md b/ticdc/ticdc-open-api.md
@@ -148,17 +148,17 @@ The configuration parameters of sink are as follows:
 {
   "dispatchers":[
     {"matcher":["test1.*", "test2.*"], "dispatcher":"ts"},
-    {"matcher":["test3.*", "test4.*"], "dispatcher":"rowid"}
+    {"matcher":["test3.*", "test4.*"], "dispatcher":"index-value"}
   ],
   "protocal":"canal-json"
 }
 ```
 
-`dispatchers`: For the sink of MQ type, you can use dispatchers to configure the event dispatcher. Four dispatchers are supported: `default`, `ts`, `rowid`, and `table`. The dispatcher rules are as follows:
+`dispatchers`: For the sink of MQ type, you can use dispatchers to configure the event dispatcher. Four dispatchers are supported: `default`, `ts`, `index-value`, and `table`. The dispatcher rules are as follows:
 
 - `default`: dispatches events in the `table` mode.
 - `ts`: uses the commitTs of the row change to create the hash value and dispatch events.
-- `rowid`: uses the name and value of the selected HandleKey column to create the hash value and dispatch events.
+- `index-value`: uses the name and value of the selected HandleKey column to create the hash value and dispatch events.
 - `table`: uses the schema name of the table and the table name to create the hash value and dispatch events.
 
 `matcher`: The matching syntax of matcher is the same as the filter rule syntax.
diff --git a/tidb-cloud/notification-2024-04-11-dm-feature-maintenance.md b/tidb-cloud/notification-2024-04-11-dm-feature-maintenance.md
@@ -0,0 +1,49 @@
+---
+title: 2024-04-11 TiDB Cloud Data Migration (DM) Feature Maintenance Notification
+summary: Learn about the details of TiDB Cloud Data Migration (DM) feature maintenance on April 11, 2024, such as the maintenance window and impact.
+---
+
+# [2024-04-11] TiDB Cloud Data Migration (DM) Feature Maintenance Notification
+
+This notification describes the details that you need to know about the maintenance for [Data Migration (DM) feature](/tidb-cloud/migrate-from-mysql-using-data-migration.md) of TiDB Cloud Dedicated on April 11, 2024.
+
+## Maintenance window
+
+- Start time: 2024-04-11 08:00 (UTC+0)
+- End time: 2024-04-11 09:00 (UTC+0)
+- Duration: 1 hour
+
+## Impact
+
+During the maintenance window, the DM feature for TiDB Dedicated clusters in the following regions will be affected:
+
+- Cloud provider: AWS, region: Oregon (us-west-2)
+- Cloud provider: AWS, region: N. Virginia (us-east-1)
+- Cloud provider: AWS, region: Singapore (ap-southeast-1)
+- Cloud provider: AWS, region: Seoul (ap-northeast-2)
+- Cloud provider: AWS, region: Frankfurt (eu-central-1)
+- Cloud provider: AWS, region: São Paulo (sa-east-1)
+- Cloud provider: AWS, region: Oregon (us-west-2)
+- Cloud provider: Google Cloud, region: Oregon (us-west1)
+- Cloud provider: Google Cloud, region: Tokyo (asia-northeast1)
+- Cloud provider: Google Cloud, region: Singapore (asia-southeast1)
+
+The maintenance only affects the DM feature in the TiDB cluster. All the other functionalities remain unaffected. You can continue to manage the TiDB cluster and perform read/write operations or other operations as usual.
+
+For clusters deployed on AWS:
+
+- During the upgrade, the DM tasks can keep running without disruption. The DM console can be used normally.
+
+For clusters deployed on Google Cloud:
+
+- The DM console will be unavailable for up to 30 minutes. During this period, you cannot create or manage DM tasks.
+- If a DM task is in the incremental migration stage, it will be interrupted for up to 30 minutes. During this period, do not purge the binary log of the MySQL database. The DM task will automatically resume after the upgrade is completed.
+- If a DM task is in the stage of exporting and importing full data, it will fail during the upgrade, and cannot be resumed after the upgrade. It is recommended not to create any DM task on the day when the upgrade is performed, to ensure that no DM tasks are in the stage of exporting and importing full data when the upgrade starts.
+
+## Completion and resumption
+
+Once the maintenance is successfully completed, the affected functionalities will be reinstated, offering you a better experience.
+
+## Get support
+
+If you have any questions or need assistance, contact our [support team](/tidb-cloud/tidb-cloud-support.md). We are here to address your concerns and provide any necessary guidance.
diff --git a/tidb-cloud/notification-2024-04-18-dm-feature-maintenance.md b/tidb-cloud/notification-2024-04-18-dm-feature-maintenance.md
@@ -0,0 +1,30 @@
+---
+title: 2024-04-18 TiDB Cloud Data Migration (DM) Feature Maintenance Notification
+summary: Learn about the details of TiDB Cloud Data Migration (DM) feature maintenance on April 18, 2024, such as the maintenance window and impact.
+---
+
+# [2024-04-18] TiDB Cloud Data Migration (DM) Feature Maintenance Notification
+
+This notification describes the details that you need to know about the maintenance for [Data Migration (DM) feature](/tidb-cloud/migrate-from-mysql-using-data-migration.md) of TiDB Cloud Dedicated on April 18, 2024.
+
+## Maintenance window
+
+- Start time: 2024-04-18 08:00 (UTC+0)
+- End time: 2024-04-18 09:00 (UTC+0)
+- Duration: 1 hour
+
+## Impact
+
+During the maintenance window, the DM feature for TiDB Dedicated clusters in the following region will be upgraded:
+
+- Cloud provider: AWS, region: Tokyo (ap-northeast-1)
+
+During the upgrade, you can use the functionalities of TiDB clusters and the DM console normally. The DM tasks can keep running without disruption.
+
+## Completion and resumption
+
+Once the maintenance is successfully completed, the affected functionalities will be reinstated, offering you a better experience.
+
+## Get support
+
+If you have any questions or need assistance, contact our [support team](/tidb-cloud/tidb-cloud-support.md). We are here to address your concerns and provide any necessary guidance.
