Merge branch 'release-8.5' into feature/preview-premium

Author: Oreoxmt

.github/workflows/link.yaml

@@ -19,10 +19,11 @@ jobs:
       - name: Check Links
         uses: lycheeverse/lychee-action@v1.6.1
         with:
-          # For parameter description, see https://github.com/lycheeverse/lychee#commandline-parameters
-          # Accept 429 for now due to github rate limit.
-          # See https://github.com/lycheeverse/lychee/issues/634
-          args: -E --exclude-mail -i -n -t 45 -- **/*.md *.md
+          # Don't fail as we want the workflow to continue and run 'Create Issue From File'
+          # Excluding releases paths as historic releases may have outdated links.
+          fail: false
+          failIfEmpty: false
+          args: --root-dir $(pwd) --cache --max-cache-age 8d -E -i -n -t 45 --exclude-path '^./releases/' --exclude-path '^./tidb-cloud/releases/' --exclude-path '^./resources/' .
           output: out.md
         env:
           GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}

.lycheeignore

@@ -3,6 +3,9 @@ https://github\.com/.*/issues/?
 https://github\.com/.*/pull/?
 https://github\.com/.*/pull/[0-9]+
 https://github\.com/.*/issues/[0-9]+
+https://github\.com/pingcap/tiflow/blob/master/dm/docs/.*
+https://github\.com/\$user/(docs|docs-cn)
+https://.*github.*/%7B%7B%7B%20.tidb_operator_version%20%7D%7D%7D
 https?://\$?\{host}/dashboard.*
 http://xn--\$?\{ip}-m86ht9t5l1bhz9ayu7b:3000.*
 http://ip:2379.*
@@ -14,7 +17,6 @@ file://.*?http:/\$%7BPD_IP%7D:\$%7BPD_PORT%7D/dashboard.*
 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://dev\.mysql\.com/doc/.+/5.7/en/.*
 https://dev\.mysql\.com/doc/.+/8\.0/en/.*
@@ -27,6 +29,7 @@ https://bugs\.mysql\.com/bug\.php.*
 https://www\.mysql\.com/products/.*
 https://help\.openai\.com/en/articles/.*
 https://platform\.openai\.com/docs/.*
+https://platform\.openai\.com/api-keys
 https://openai\.com/.*
 https://jwt\.io/
 https://typeorm\.io/.*
@@ -36,3 +39,9 @@ https://docs\.pingcap\.com/tidb/v6\.6/system-variables#tidb_pessimistic_txn_aggr
 https://docs\.pingcap\.com/tidb/v7\.6/system-variables#tidb_ddl_version-new-in-v760
 https://developers\.redhat\.com/blog/2021/01/05/building-red-hat-enterprise-linux-9-for-the-x86-64-v2-microarchitecture-level
 https://portal\.azure\.com/.*
+https://.*github.*/%7B%7B%7B%20.tidb_operator_version%20%7D%7D%7D
+https://.*github.*/%7B%7B%7B.tidb-operator-version%7D%7D%7D
+https://portal\.azure\.com/.*
+https://azuremarketplace\.microsoft\.com/.*
+https://one\.newrelic\.com/.*
+https://tidbcloud\.com/.*

best-practices/_index.md

@@ -23,6 +23,7 @@ Learn best practices for designing schemas in TiDB, including managing DDL opera
 | ------------------- | ----------- |
 | [Manage DDL](/best-practices/ddl-introduction.md) | Best practices for managing Data Definition Language (DDL) operations in TiDB. |
 | [Use UUIDs as Primary Keys](/best-practices/uuid.md) | Best practices for storing and indexing UUIDs (Universally Unique Identifiers) efficiently when using UUIDs as primary keys. |
+| [Use TiDB Partitioned Tables](/best-practices/tidb-partitioned-tables-best-practices.md) | Best practices for using TiDB partitioned tables to improve performance, simplify data management, and efficiently handle large-scale datasets. |
 | [Optimize Multi-Column Indexes](/best-practices/multi-column-index-best-practices.md) | Best practices for designing and using multi-column indexes in TiDB to improve query performance. |
 | [Manage Indexes and Identify Unused Indexes](/best-practices/index-management-best-practices.md) | Best practices for managing and optimizing indexes, identifying and removing unused indexes in TiDB to optimize performance. |
 

dm/dm-compatibility-catalog.md

@@ -14,18 +14,18 @@ DM supports migrating data from different sources to TiDB clusters. Based on the
 
 ## Data sources
 
-| Data source | Compatibility level | Note |
-| - | - | - |
-| MySQL ≤ 5.5 | Not tested | |
-| MySQL 5.6 | GA | |
-| MySQL 5.7 | GA | |
-| MySQL 8.0 | GA | Does not support [binlog transaction compression (`Transaction_payload_event`)](https://dev.mysql.com/doc/refman/8.0/en/binary-log-transaction-compression.html). |
-| MySQL 8.1 ~ 8.3 | Not tested | Does not support [binlog transaction compression (`Transaction_payload_event`)](https://dev.mysql.com/doc/refman/8.0/en/binary-log-transaction-compression.html). |
-| MySQL 8.4 | Experimental (supported starting from TiDB v8.5.6) | Does not support [binlog transaction compression (`Transaction_payload_event`)](https://dev.mysql.com/doc/refman/8.4/en/binary-log-transaction-compression.html). |
-| MySQL 9.x | Not tested | |
-| MariaDB < 10.1.2 | Incompatible | Incompatible with binlog of the time type. |
-| MariaDB 10.1.2 ~ 10.5.10 | Experimental | |
-| MariaDB > 10.5.10 | Not tested | Expected to work in most cases after bypassing the [precheck](/dm/dm-precheck.md). See [MariaDB notes](#mariadb-notes). |
+| Data source              | Compatibility level | Note |
+| ------------------------ | ------------------- | ---- |
+| MySQL ≤ 5.5              | Not tested          |      |
+| MySQL 5.6                | GA                  |      |
+| MySQL 5.7                | GA                  |      |
+| MySQL 8.0                | GA                  | Does not support [binlog transaction compression (`Transaction_payload_event`)](https://dev.mysql.com/doc/refman/8.0/en/binary-log-transaction-compression.html). |
+| MySQL 8.1 ~ 8.3          | Not tested          | Does not support [binlog transaction compression (`Transaction_payload_event`)](https://dev.mysql.com/doc/refman/8.0/en/binary-log-transaction-compression.html). |
+| MySQL 8.4                | Experimental (supported starting from TiDB v8.5.6) | Does not support [binlog transaction compression (`Transaction_payload_event`)](https://dev.mysql.com/doc/refman/8.4/en/binary-log-transaction-compression.html). |
+| MySQL 9.x                | Not tested          |      |
+| MariaDB < 10.1.2         | Incompatible        | Incompatible with binlog of the time type. |
+| MariaDB 10.1.2 ~ 10.5.10 | Experimental        |      |
+| MariaDB > 10.5.10        | Not tested          | Expected to work in most cases after bypassing the [precheck](/dm/dm-precheck.md). See [MariaDB notes](#mariadb-notes). |
 
 ### Foreign key `CASCADE` operations
 

dm/dm-precheck.md

@@ -131,6 +131,7 @@ For the incremental data migration mode (`task-mode: incremental`), in addition
     - Check whether binlog is enabled (required by DM).
     - Check whether `binlog_format=ROW` is configured (DM only supports the migration of binlog in the ROW format).
     - Check whether `binlog_row_image=FULL` is configured (DM only supports `binlog_row_image=FULL`).
+    - Check whether `binlog_transaction_compression=OFF` is configured (DM does not support transaction compression).
     - If `binlog_do_db` or `binlog_ignore_db` is configured, check whether the database tables to be migrated meet the conditions of `binlog_do_db` and `binlog_ignore_db`.
 
 * (Mandatory) Check if the upstream database is in an [Online-DDL](/dm/feature-online-ddl.md) process (in which the `ghost` table is created but the `rename` phase is not executed yet). If the upstream is in the online-DDL process, the precheck returns an error. In this case, wait until the DDL to complete and retry.
@@ -143,21 +144,21 @@ For the full and incremental data migration mode (`task-mode: all`), in addition
 
 Prechecks can find potential risks in your environments. It is not recommended to ignore check items. If your data migration task has special needs, you can use the [`ignore-checking-items` configuration item](/dm/task-configuration-file-full.md#task-configuration-file-template-advanced) to skip some check items.
 
-| Check item  | Description   |
-| :---------- | :------------ |
-| `dump_privilege`         | Checks the dump privilege of the user in the upstream MySQL instance. |
-| `replication_privilege` | Checks the replication privilege of the user in the upstream MySQL instance. |
-| `version`               | Checks the version of the upstream database. |
-| `server_id`             | Checks whether server_id is configured in the upstream database. |
-| `binlog_enable`         | Checks whether binlog is enabled in the upstream database. |
-| `table_schema`          | Checks the compatibility of the table schemas in the upstream MySQL tables. |
-| `schema_of_shard_tables`| Checks the consistency of the table schemas in the upstream MySQL multi-instance shards. |
-| `auto_increment_ID`     | Checks whether the auto-increment primary key conflicts in the upstream MySQL multi-instance shards. |
-|`online_ddl`| Checks whether the upstream is in the process of [online-DDL](/dm/feature-online-ddl.md). |
-| `empty_region` | Checks the number of empty Regions in the downstream database for physical import. |
-| `region_distribution` | Checks the distribution of Regions in the downstream database for physical import. |
-| `downstream_version` | Checks the versions of TiDB, PD, and TiKV in the downstream database. |
-| `free_space` | Checks the free space of the downstream database. |
+| Check item                  | Description   |
+| :-------------------------- | :------------ |
+| `dump_privilege`            | Checks the dump privilege of the user in the upstream MySQL instance. |
+| `replication_privilege`     | Checks the replication privilege of the user in the upstream MySQL instance. |
+| `version`                   | Checks the version of the upstream database. |
+| `server_id`                 | Checks whether server_id is configured in the upstream database. |
+| `binlog_enable`             | Checks whether binlog is enabled in the upstream database. |
+| `table_schema`              | Checks the compatibility of the table schemas in the upstream MySQL tables. |
+| `schema_of_shard_tables`    | Checks the consistency of the table schemas in the upstream MySQL multi-instance shards. |
+| `auto_increment_ID`         | Checks whether the auto-increment primary key conflicts in the upstream MySQL multi-instance shards. |
+| `online_ddl`                | Checks whether the upstream is in the process of [online-DDL](/dm/feature-online-ddl.md). |
+| `empty_region`              | Checks the number of empty Regions in the downstream database for physical import. |
+| `region_distribution`       | Checks the distribution of Regions in the downstream database for physical import. |
+| `downstream_version`        | Checks the versions of TiDB, PD, and TiKV in the downstream database. |
+| `free_space`                | Checks the free space of the downstream database. |
 | `downstream_mutex_features` | Checks whether the downstream database is running tasks that are incompatible with physical import. |
 
 > **Note:**

explore-htap.md

@@ -108,7 +108,7 @@ If any issue occurs during using TiDB, refer to the following documents:
 - [TiDB cluster troubleshooting guide](/troubleshoot-tidb-cluster.md)
 - [Troubleshoot a TiFlash Cluster](/tiflash/troubleshoot-tiflash.md)
 
-You are also welcome to create [GitHub Issues](https://github.com/pingcap/tiflash/issues) or submit your questions on [AskTUG](https://asktug.com/).
+You are also welcome to create [GitHub Issues](https://github.com/pingcap/tiflash/issues) or ask the community on [Discord](https://discord.gg/DQZ2dy3cuc?utm_source=doc) or [Slack](https://slack.tidb.io/invite?team=tidb-community&channel=everyone&ref=pingcap-docs).
 
 ## What's next
 

faq/manage-cluster-faq.md

@@ -109,7 +109,7 @@ You can scale TiDB as your business grows.
 
 ### If Percolator uses distributed locks and the crash client keeps the lock, will the lock not be released?
 
-For more details, see [Percolator and TiDB Transaction Algorithm](https://tidb.net/blog/f537be2c) in Chinese.
+For more details, see [Percolator and TiDB Transaction Algorithm](https://pingkai.cn/tidbcommunity/blog/f537be2c) in Chinese.
 
 ### Why does TiDB use gRPC instead of Thrift? Is it because Google uses it?
 

mysql-schema/mysql-schema.md

@@ -33,6 +33,7 @@ These system tables contain grant information about user accounts and their priv
     * `tidb_server_version`: the version information of TiDB when it is initialized. Note that this value is read-only and cannot be modified.
     * `system_tz`: the system time zone of TiDB.
     * `new_collation_enabled`: whether TiDB has enabled the [new framework for collations](/character-set-and-collation.md#new-framework-for-collations). Note that this value is read-only and cannot be modified.
+    * `cluster_id` (New in v8.5.6): the unique identifier of the TiDB cluster. Note that this value is read-only and cannot be modified.
 
 ## Server-side help system tables