From fa1f3591bb44cba2906070fb6a1af6fd70919b8f Mon Sep 17 00:00:00 2001 From: qiancai Date: Tue, 25 Feb 2025 18:06:42 +0800 Subject: [PATCH 01/10] updated the outdated content --- tidb-cloud/import-with-mysql-cli.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/tidb-cloud/import-with-mysql-cli.md b/tidb-cloud/import-with-mysql-cli.md index bc42207d5f4b7..2bf0a83b3a1b7 100644 --- a/tidb-cloud/import-with-mysql-cli.md +++ b/tidb-cloud/import-with-mysql-cli.md @@ -20,9 +20,13 @@ Connect to your TiDB cluster. 1. Navigate to the [**Clusters**](https://tidbcloud.com/console/clusters) page, and then click the name of your target cluster to go to its overview page. -2. Click **Connect** in the upper-right corner. A connection dialog is displayed. +2. In the left navigation pane, click **Networking**. -3. Click **Allow Access from Anywhere**. +3. On the **Networking** page, click **Add IP Address** in the **IP Access List** area. + +4. In the dialog, choose **Allow access from anywhere**, and then click **Confirm**. + +5. In the upper-right corner, click **Connect** to open the dialog for connection information. For more details about how to obtain the connection string, see [Connect to TiDB Cloud Dedicated via Public Connection](/tidb-cloud/connect-via-standard-connection.md). From d8616d2d2607755b362e932a864291230f930d12 Mon Sep 17 00:00:00 2001 From: qiancai Date: Tue, 25 Feb 2025 18:07:00 +0800 Subject: [PATCH 02/10] add a note for using MySQL v8.0 on macOS --- tidb-cloud/connect-via-standard-connection.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tidb-cloud/connect-via-standard-connection.md b/tidb-cloud/connect-via-standard-connection.md index 9b7cecd457c6b..c51af60f107c3 100644 --- a/tidb-cloud/connect-via-standard-connection.md +++ b/tidb-cloud/connect-via-standard-connection.md @@ -39,6 +39,10 @@ To connect to a TiDB Cloud Dedicated cluster via public connection, take the fol 5. Choose your preferred connection method, and then refer to the connection string and sample code on the tab to connect to your cluster. +> **Note:** +> +> The MySQL v9.0 client on macOS cannot correctly load the `mysql_native_password` plugin, causing the error `ERROR 2059 (HY000): Authentication plugin 'mysql_native_password' cannot be loaded` when connecting to TiDB. To address this issue, it is recommended to install and use the MySQL v8.0 client to connect to TiDB. + ## What's next After you have successfully connected to your TiDB cluster, you can [explore SQL statements with TiDB](/basic-sql-operations.md). From 3973a42f23a67539eaa0ec6655c61e8fe8820d41 Mon Sep 17 00:00:00 2001 From: qiancai Date: Tue, 25 Feb 2025 18:07:33 +0800 Subject: [PATCH 03/10] add bin log format check as a prerequisite --- tidb-cloud/migrate-from-mysql-using-data-migration.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/tidb-cloud/migrate-from-mysql-using-data-migration.md b/tidb-cloud/migrate-from-mysql-using-data-migration.md index 392f9d0102143..183b170357883 100644 --- a/tidb-cloud/migrate-from-mysql-using-data-migration.md +++ b/tidb-cloud/migrate-from-mysql-using-data-migration.md @@ -145,7 +145,14 @@ If your MySQL service is in a Google Cloud VPC, take the following steps: ### Enable binary logs -To perform incremental data migration, make sure you have enabled binary logs of the upstream database, and the binary logs have been kept for more than 24 hours. +To perform incremental data migration, make sure the following requirements are met: + +- Binary logs are enabled for the upstream database. +- The binary logs are retained for at least 24 hours. +- The binlog format for the upstream database is set to `ROW`. If not, update the format to `ROW` as follows to avoid the [format error](/tidb-cloud/tidb-cloud-dm-precheck-and-troubleshooting.md#error-message-check-whether-mysql-binlog_format-is-row): + + - MySQL: execute the `set global binlog_format=ROW;` statement. + - AWS Aurora (MySQL) or RDS MySQL: follow the instructions in [AWS documentation](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithDBInstanceParamGroups.html) to create a new DB parameter group. Set the `binlog_format=row` parameter in the new DB parameter group, modify the instance to use the new DB parameter group, and then restart the instance to take effect. ## Step 1: Go to the **Data Migration** page From ac11eb12df29f1b209582f118172eca70e4bfd26 Mon Sep 17 00:00:00 2001 From: qiancai Date: Wed, 26 Feb 2025 10:07:37 +0800 Subject: [PATCH 04/10] remove the space after -p --- tidb-cloud/connect-via-standard-connection.md | 4 ---- tidb-cloud/import-with-mysql-cli.md | 5 +++-- 2 files changed, 3 insertions(+), 6 deletions(-) diff --git a/tidb-cloud/connect-via-standard-connection.md b/tidb-cloud/connect-via-standard-connection.md index c51af60f107c3..9b7cecd457c6b 100644 --- a/tidb-cloud/connect-via-standard-connection.md +++ b/tidb-cloud/connect-via-standard-connection.md @@ -39,10 +39,6 @@ To connect to a TiDB Cloud Dedicated cluster via public connection, take the fol 5. Choose your preferred connection method, and then refer to the connection string and sample code on the tab to connect to your cluster. -> **Note:** -> -> The MySQL v9.0 client on macOS cannot correctly load the `mysql_native_password` plugin, causing the error `ERROR 2059 (HY000): Authentication plugin 'mysql_native_password' cannot be loaded` when connecting to TiDB. To address this issue, it is recommended to install and use the MySQL v8.0 client to connect to TiDB. - ## What's next After you have successfully connected to your TiDB cluster, you can [explore SQL statements with TiDB](/basic-sql-operations.md). diff --git a/tidb-cloud/import-with-mysql-cli.md b/tidb-cloud/import-with-mysql-cli.md index 2bf0a83b3a1b7..81015d2e3c5de 100644 --- a/tidb-cloud/import-with-mysql-cli.md +++ b/tidb-cloud/import-with-mysql-cli.md @@ -63,12 +63,13 @@ Do the following to import data from an SQL file: 2. Use the following command to import data from the SQL file: ```bash - mysql --comments --connect-timeout 150 -u '' -h -P 4000 -D test --ssl-mode=VERIFY_IDENTITY --ssl-ca= -p < product_data.sql + mysql --comments --connect-timeout 150 -u '' -h -P 4000 -D test --ssl-mode=VERIFY_IDENTITY --ssl-ca= -p < product_data.sql ``` > **Note:** > -> The default database name used here is `test`, and you can either manually create your own database or use the `CREATE DATABASE` command in an SQL file. +> - The default database name used here is `test`, and you can either manually create your own database or use the `CREATE DATABASE` command in an SQL file. +> - The MySQL v9.0 client on macOS cannot correctly load the `mysql_native_password` plugin, causing the error `ERROR 2059 (HY000): Authentication plugin 'mysql_native_password' cannot be loaded` when connecting to TiDB. To address this issue, it is recommended to install and use the MySQL v8.0 client to connect to TiDB.
From 72cb5ffe2fed0c93d52a345bf1aa5f0e900d9aae Mon Sep 17 00:00:00 2001 From: qiancai Date: Wed, 26 Feb 2025 10:11:19 +0800 Subject: [PATCH 05/10] Update import-with-mysql-cli-serverless.md --- tidb-cloud/import-with-mysql-cli-serverless.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/import-with-mysql-cli-serverless.md b/tidb-cloud/import-with-mysql-cli-serverless.md index 87e03095d02f2..4818233915b69 100644 --- a/tidb-cloud/import-with-mysql-cli-serverless.md +++ b/tidb-cloud/import-with-mysql-cli-serverless.md @@ -67,7 +67,7 @@ Do the following to import data from an SQL file: 2. Use the following command to import data from the SQL file: ```bash - mysql --comments --connect-timeout 150 -u '' -h -P 4000 -D test --ssl-mode=VERIFY_IDENTITY --ssl-ca= -p < product_data.sql + mysql --comments --connect-timeout 150 -u '' -h -P 4000 -D test --ssl-mode=VERIFY_IDENTITY --ssl-ca= -p < product_data.sql ``` > **Note:** From 7f5adb039561bc3f85c13a11692d46f8d3084c1f Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Fri, 28 Feb 2025 14:23:30 +0800 Subject: [PATCH 06/10] Update tidb-cloud/import-with-mysql-cli.md --- tidb-cloud/import-with-mysql-cli.md | 1 - 1 file changed, 1 deletion(-) diff --git a/tidb-cloud/import-with-mysql-cli.md b/tidb-cloud/import-with-mysql-cli.md index 81015d2e3c5de..0edf769ad56df 100644 --- a/tidb-cloud/import-with-mysql-cli.md +++ b/tidb-cloud/import-with-mysql-cli.md @@ -69,7 +69,6 @@ Do the following to import data from an SQL file: > **Note:** > > - The default database name used here is `test`, and you can either manually create your own database or use the `CREATE DATABASE` command in an SQL file. -> - The MySQL v9.0 client on macOS cannot correctly load the `mysql_native_password` plugin, causing the error `ERROR 2059 (HY000): Authentication plugin 'mysql_native_password' cannot be loaded` when connecting to TiDB. To address this issue, it is recommended to install and use the MySQL v8.0 client to connect to TiDB.
From 3c41fa350328157dffda628ebde835e8c87d57c7 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Fri, 28 Feb 2025 14:23:47 +0800 Subject: [PATCH 07/10] Update tidb-cloud/import-with-mysql-cli.md --- tidb-cloud/import-with-mysql-cli.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/import-with-mysql-cli.md b/tidb-cloud/import-with-mysql-cli.md index 0edf769ad56df..314783d437da4 100644 --- a/tidb-cloud/import-with-mysql-cli.md +++ b/tidb-cloud/import-with-mysql-cli.md @@ -68,7 +68,7 @@ Do the following to import data from an SQL file: > **Note:** > -> - The default database name used here is `test`, and you can either manually create your own database or use the `CREATE DATABASE` command in an SQL file. +> The default database name used here is `test`, and you can either manually create your own database or use the `CREATE DATABASE` command in an SQL file.
From 6d2bead3bd21bee97f9997dc9057afabd28fb1ba Mon Sep 17 00:00:00 2001 From: qiancai Date: Fri, 28 Feb 2025 16:02:13 +0800 Subject: [PATCH 08/10] sync .lycheeignore from master --- .lycheeignore | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/.lycheeignore b/.lycheeignore index ce919d2c77c0f..9c1e0c7f4165d 100644 --- a/.lycheeignore +++ b/.lycheeignore @@ -15,4 +15,19 @@ http://\{grafana-ip\}:3000 http://\{pd-ip\}:2379/dashboard http://localhost:\d+/ https://github\.com/\$user/(docs|docs-cn) -https://linux.die.net/man.* +https://linux\.die\.net/man.* +https://dev\.mysql\.com/doc/.+/5.7/en/.* +https://dev\.mysql\.com/doc/.+/8\.0/en/.* +https://dev\.mysql\.com/doc/.+/8\.4/en/.* +https://dev\.mysql\.com/doc/[a-z\-]+/en/.* +https://dev\.mysql\.com/doc/relnotes/[a-z\-]+/en/.* +https://dev\.mysql\.com/doc/dev/mysql-server/.* +https://dev\.mysql\.com/downloads/.* +https://bugs\.mysql\.com/bug\.php.* +https://www\.mysql\.com/products/.* +https://platform\.openai\.com/docs/.* +https://openai\.com/.* +https://jwt\.io/ +https://typeorm\.io/.* +https://dash\.cloudflare\.com/.* +https://centminmod\.com/mydumper\.html From 923d2db99227581519eeaaf3bac86191abe34438 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Tue, 4 Mar 2025 15:07:12 +0800 Subject: [PATCH 09/10] Update tidb-cloud/migrate-from-mysql-using-data-migration.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Daniël van Eeden --- tidb-cloud/migrate-from-mysql-using-data-migration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/migrate-from-mysql-using-data-migration.md b/tidb-cloud/migrate-from-mysql-using-data-migration.md index 183b170357883..3f398fc90c096 100644 --- a/tidb-cloud/migrate-from-mysql-using-data-migration.md +++ b/tidb-cloud/migrate-from-mysql-using-data-migration.md @@ -151,7 +151,7 @@ To perform incremental data migration, make sure the following requirements are - The binary logs are retained for at least 24 hours. - The binlog format for the upstream database is set to `ROW`. If not, update the format to `ROW` as follows to avoid the [format error](/tidb-cloud/tidb-cloud-dm-precheck-and-troubleshooting.md#error-message-check-whether-mysql-binlog_format-is-row): - - MySQL: execute the `set global binlog_format=ROW;` statement. + - MySQL: execute the `SET GLOBAL binlog_format=ROW;` statement. If you want to persist this change across reboots, you can execute the `SET PERSIST binlog_format=ROW;` statement. - AWS Aurora (MySQL) or RDS MySQL: follow the instructions in [AWS documentation](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithDBInstanceParamGroups.html) to create a new DB parameter group. Set the `binlog_format=row` parameter in the new DB parameter group, modify the instance to use the new DB parameter group, and then restart the instance to take effect. ## Step 1: Go to the **Data Migration** page From 0dfebad8e0c9c6446b9db35d7a23120a0bf5a682 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Tue, 4 Mar 2025 16:40:18 +0800 Subject: [PATCH 10/10] Update tidb-cloud/migrate-from-mysql-using-data-migration.md Co-authored-by: Lilian Lee --- tidb-cloud/migrate-from-mysql-using-data-migration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/migrate-from-mysql-using-data-migration.md b/tidb-cloud/migrate-from-mysql-using-data-migration.md index 3f398fc90c096..6032d21a157e5 100644 --- a/tidb-cloud/migrate-from-mysql-using-data-migration.md +++ b/tidb-cloud/migrate-from-mysql-using-data-migration.md @@ -152,7 +152,7 @@ To perform incremental data migration, make sure the following requirements are - The binlog format for the upstream database is set to `ROW`. If not, update the format to `ROW` as follows to avoid the [format error](/tidb-cloud/tidb-cloud-dm-precheck-and-troubleshooting.md#error-message-check-whether-mysql-binlog_format-is-row): - MySQL: execute the `SET GLOBAL binlog_format=ROW;` statement. If you want to persist this change across reboots, you can execute the `SET PERSIST binlog_format=ROW;` statement. - - AWS Aurora (MySQL) or RDS MySQL: follow the instructions in [AWS documentation](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithDBInstanceParamGroups.html) to create a new DB parameter group. Set the `binlog_format=row` parameter in the new DB parameter group, modify the instance to use the new DB parameter group, and then restart the instance to take effect. + - Amazon Aurora MySQL or RDS for MySQL: follow the instructions in [AWS documentation](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithDBInstanceParamGroups.html) to create a new DB parameter group. Set the `binlog_format=row` parameter in the new DB parameter group, modify the instance to use the new DB parameter group, and then restart the instance to take effect. ## Step 1: Go to the **Data Migration** page