bump versions to v5.3.2

pingcap · Jun 28, 2022 · 05dda79 · 05dda79
1 parent 8cc3221
commit 05dda79
Show file tree

Hide file tree

Showing 11 changed files with 32 additions and 32 deletions.
diff --git a/download-ecosystem-tools.md b/download-ecosystem-tools.md
@@ -25,7 +25,7 @@ If you want to download the latest version of [TiDB Binlog](/tidb-binlog/tidb-bi
 
 > **Note:**
 >
-> `{version}` in the above download link indicates the version number of TiDB. For example, the download link for `v5.3.1` is `https://download.pingcap.org/tidb-v5.3.1-linux-amd64.tar.gz`.
+> `{version}` in the above download link indicates the version number of TiDB. For example, the download link for `v5.3.2` is `https://download.pingcap.org/tidb-v5.3.2-linux-amd64.tar.gz`.
 
 ## TiDB Lightning
 
@@ -37,7 +37,7 @@ Download [TiDB Lightning](/tidb-lightning/tidb-lightning-overview.md) by using t
 
 > **Note:**
 >
-> `{version}` in the above download link indicates the version number of TiDB Lightning. For example, the download link for `v5.3.1` is `https://download.pingcap.org/tidb-toolkit-v5.3.1-linux-amd64.tar.gz`.
+> `{version}` in the above download link indicates the version number of TiDB Lightning. For example, the download link for `v5.3.2` is `https://download.pingcap.org/tidb-toolkit-v5.3.2-linux-amd64.tar.gz`.
 
 ## BR (backup and restore)
 
@@ -49,7 +49,7 @@ Download [BR](/br/backup-and-restore-tool.md) by using the download link in the
 
 > **Note:**
 >
-> `{version}` in the above download link indicates the version number of BR. For example, the download link for `v5.3.1` is `https://download.pingcap.org/tidb-toolkit-v5.3.1-linux-amd64.tar.gz`.
+> `{version}` in the above download link indicates the version number of BR. For example, the download link for `v5.3.2` is `https://download.pingcap.org/tidb-toolkit-v5.3.2-linux-amd64.tar.gz`.
 
 ## TiDB DM (Data Migration)
 
@@ -61,7 +61,7 @@ Download [DM](https://docs.pingcap.com/tidb-data-migration/stable/overview) by u
 
 > **Note:**
 >
-> `{version}` in the above download link indicates the version number of DM. For example, the download link for `v5.3.1` is `https://download.pingcap.org/dm-v5.3.1-linux-amd64.tar.gz`. You can check the published DM versions in the [DM Release](https://github.com/pingcap/dm/releases) page.
+> `{version}` in the above download link indicates the version number of DM. For example, the download link for `v5.3.2` is `https://download.pingcap.org/dm-v5.3.2-linux-amd64.tar.gz`. You can check the published DM versions in the [DM Release](https://github.com/pingcap/dm/releases) page.
 
 ## Dumpling
 
@@ -73,7 +73,7 @@ Download [Dumpling](/dumpling-overview.md) from the links below:
 
 > **Note:**
 >
-> The `{version}` in the download link is the version number of Dumpling. For example, the link for downloading the `v5.3.1` version of Dumpling is `https://download.pingcap.org/tidb-toolkit-v5.3.1-linux-amd64.tar.gz`. You can view the currently released versions in [TiDB Releases](https://github.com/pingcap/tidb/releases).
+> The `{version}` in the download link is the version number of Dumpling. For example, the link for downloading the `v5.3.2` version of Dumpling is `https://download.pingcap.org/tidb-toolkit-v5.3.2-linux-amd64.tar.gz`. You can view the currently released versions in [TiDB Releases](https://github.com/pingcap/tidb/releases).
 >
 > Dumpling supports arm64 linux. You can replace `amd64` in the download link with `arm64`, which means the `arm64` version of Dumpling.
 

diff --git a/pd-control.md b/pd-control.md
@@ -27,7 +27,7 @@ If you want to download the latest version of `pd-ctl`, directly download the Ti
 
 > **Note:**
 >
-> `{version}` indicates the version number of TiDB. For example, if `{version}` is `v5.3.1`, the package download link is `https://download.pingcap.org/tidb-v5.3.1-linux-amd64.tar.gz`.
+> `{version}` indicates the version number of TiDB. For example, if `{version}` is `v5.3.2`, the package download link is `https://download.pingcap.org/tidb-v5.3.2-linux-amd64.tar.gz`.
 
 ### Compile from source code
 

diff --git a/pd-recover.md b/pd-recover.md
@@ -26,7 +26,7 @@ To download the latest version of PD Recover, directly download the TiDB package
 
 > **Note:**
 >
-> `{version}` indicates the version number of TiDB. For example, if `{version}` is `v5.3.1`, the package download link is `https://download.pingcap.org/tidb-v5.3.1-linux-amd64.tar.gz`.
+> `{version}` indicates the version number of TiDB. For example, if `{version}` is `v5.3.2`, the package download link is `https://download.pingcap.org/tidb-v5.3.2-linux-amd64.tar.gz`.
 
 ## Quick Start
 

diff --git a/production-deployment-using-tiup.md b/production-deployment-using-tiup.md
@@ -309,13 +309,13 @@ Then execute the `deploy` command to deploy the TiDB cluster:
 {{< copyable "shell-regular" >}}
 
 ```shell
-tiup cluster deploy tidb-test v5.3.1 ./topology.yaml --user root [-p] [-i /home/root/.ssh/gcp_rsa]
+tiup cluster deploy tidb-test v5.3.2 ./topology.yaml --user root [-p] [-i /home/root/.ssh/gcp_rsa]
 ```
 
 In the above command:
 
 - The name of the deployed TiDB cluster is `tidb-test`.
-- You can see the latest supported versions by running `tiup list tidb`. This document takes `v5.3.1` as an example.
+- You can see the latest supported versions by running `tiup list tidb`. This document takes `v5.3.2` as an example.
 - The initialization configuration file is `topology.yaml`.
 - `--user root`: Log in to the target machine through the `root` key to complete the cluster deployment, or you can use other users with `ssh` and `sudo` privileges to complete the deployment.
 - `[-i]` and `[-p]`: optional. If you have configured login to the target machine without password, these parameters are not required. If not, choose one of the two parameters. `[-i]` is the private key of the `root` user (or other users specified by `--user`) that has access to the target machine. `[-p]` is used to input the user password interactively.
@@ -337,7 +337,7 @@ TiUP supports managing multiple TiDB clusters. The command above outputs informa
 Starting /home/tidb/.tiup/components/cluster/v1.5.0/cluster list
 Name              User  Version        Path                                                        PrivateKey
 ----              ----  -------        ----                                                        ----------
-tidb-test         tidb  v5.3.1      /home/tidb/.tiup/storage/cluster/clusters/tidb-test         /home/tidb/.tiup/storage/cluster/clusters/tidb-test/ssh/id_rsa
+tidb-test         tidb  v5.3.2      /home/tidb/.tiup/storage/cluster/clusters/tidb-test         /home/tidb/.tiup/storage/cluster/clusters/tidb-test/ssh/id_rsa
 ```
 
 ## Step 6: Check the status of the deployed TiDB cluster

diff --git a/quick-start-with-tidb.md b/quick-start-with-tidb.md
@@ -64,10 +64,10 @@ As a distributed system, a basic TiDB test cluster usually consists of 2 TiDB in
         {{< copyable "shell-regular" >}}
 
         ```shell
-        tiup playground v5.3.1 --db 2 --pd 3 --kv 3
+        tiup playground v5.3.2 --db 2 --pd 3 --kv 3
         ```
 
-        The command downloads a version cluster to the local machine and starts it, such as v5.3.1. To view the latest version, run `tiup list tidb`.
+        The command downloads a version cluster to the local machine and starts it, such as v5.3.2. To view the latest version, run `tiup list tidb`.
 
         This command returns the access methods of the cluster:
 
@@ -167,10 +167,10 @@ As a distributed system, a basic TiDB test cluster usually consists of 2 TiDB in
         {{< copyable "shell-regular" >}}
 
         ```shell
-        tiup playground v5.3.1 --db 2 --pd 3 --kv 3
+        tiup playground v5.3.2 --db 2 --pd 3 --kv 3
         ```
 
-        The command downloads a version cluster to the local machine and starts it, such as v5.3.1. To view the latest version, run `tiup list tidb`.
+        The command downloads a version cluster to the local machine and starts it, such as v5.3.2. To view the latest version, run `tiup list tidb`.
 
         This command returns the access methods of the cluster:
 

diff --git a/scale-tidb-using-tiup.md b/scale-tidb-using-tiup.md
@@ -266,7 +266,7 @@ If you want to remove a TiKV node from the `10.0.1.5` host, take the following s
     ```
     Starting /root/.tiup/components/cluster/v1.7.0/cluster display <cluster-name>
     TiDB Cluster: <cluster-name>
-    TiDB Version: v5.3.1
+    TiDB Version: v5.3.2
     ID              Role         Host        Ports                            Status  Data Dir                Deploy Dir
     --              ----         ----        -----                            ------  --------                ----------
     10.0.1.3:8300   cdc          10.0.1.3    8300                             Up      data/cdc-8300           deploy/cdc-8300
@@ -396,7 +396,7 @@ In special cases (such as when a node needs to be forcibly taken down), or if th
         > **Note:**
         >
         > If multiple PD instances exist in the cluster, you only need to specify the IP address:port of an active PD instance in the above command.
-        
+
 3. Wait for the store of the TiFlash node to disappear or for the `state_name` to become `Tombstone` before you stop the TiFlash process.
 
 4. Manually delete TiFlash data files (whose location can be found in the `data_dir` directory under the TiFlash configuration of the cluster topology file).

diff --git a/ticdc/manage-ticdc.md b/ticdc/manage-ticdc.md
@@ -11,14 +11,14 @@ You can also use the HTTP interface (the TiCDC OpenAPI feature) to manage the Ti
 
 ## Upgrade TiCDC using TiUP
 
-This section introduces how to upgrade the TiCDC cluster using TiUP. In the following example, assume that you need to upgrade TiCDC and the entire TiDB cluster to v5.3.1.
+This section introduces how to upgrade the TiCDC cluster using TiUP. In the following example, assume that you need to upgrade TiCDC and the entire TiDB cluster to v5.3.2.
 
 {{< copyable "shell-regular" >}}
 
 ```shell
 tiup update --self && \
 tiup update --all && \
-tiup cluster upgrade <cluster-name> v5.3.1
+tiup cluster upgrade <cluster-name> v5.3.2
 ```
 
 ### Notes for upgrade
@@ -572,7 +572,7 @@ worker-num = 16
 # The dispatcher rules are as follows:
 # - default: When multiple unique indexes (including the primary key) exist or the Old Value feature is enabled, events are dispatched in the table mode. When only one unique index (or the primary key) exists, events are dispatched in the rowid mode.
 # - ts: Use the commitTs of the row change to create Hash and dispatch events.
-# - index-value: Use the value of the primary key or the unique index of the table to create Hash and dispatch events. 
+# - index-value: Use the value of the primary key or the unique index of the table to create Hash and dispatch events.
 # - table: Use the schema name of the table and the table name to create Hash and dispatch events.
 # The matching syntax of matcher is the same as the filter rule syntax.
 dispatchers = [

diff --git a/tidb-lightning/tidb-lightning-configuration.md b/tidb-lightning/tidb-lightning-configuration.md
@@ -111,7 +111,7 @@ driver = "file"
 # backend = "local"
 # Whether to allow importing data to tables with data. The default value is `false`.
 # When you use parallel import mode, you must set it to `true`, because multiple TiDB Lightning instances are importing the same table at the same time.
-# NOTE: this config field is introduced since v5.3.1. Ignore it when using TiDB Lightning v5.3.0.
+# NOTE: this config field is introduced since v5.3.2. Ignore it when using TiDB Lightning v5.3.0.
 # incremental-import = false
 
 # The listening address of tikv-importer when backend is "importer". Change it to the actual address.
@@ -228,14 +228,14 @@ trim-last-separator = false
 # schema = '$1'
 # table = '$2'
 # type = '$3'
-# 
+#
 # Sets rules for merging sharded schemas and tables. Specifically, import `table1` and `table2` from `my_db1`, and `table3` and `table4` from `my_db2` to `table5` in `my_db`.
 # [[routes]]
 # schema-pattern = "my_db1"
 # table-pattern = "table[1-2]"
 # target-schema = "my_db"
 # target-table = "table5"
-# 
+#
 # [[routes]]
 # schema-pattern = "my_db2"
 # table-pattern = "table[3-4]"

diff --git a/tiup/tiup-component-management.md b/tiup/tiup-component-management.md
@@ -69,12 +69,12 @@ Example 2: Use TiUP to install the nightly version of TiDB.
 tiup install tidb:nightly
 ```
 
-Example 3: Use TiUP to install TiKV v5.3.1.
+Example 3: Use TiUP to install TiKV v5.3.2.
 
 {{< copyable "shell-regular" >}}
 
 ```shell
-tiup install tikv:v5.3.1
+tiup install tikv:v5.3.2
 ```
 
 ## Upgrade components
@@ -127,12 +127,12 @@ Before the component is started, TiUP creates a directory for it, and then puts
 
 If you want to start the same component multiple times and reuse the previous working directory, you can use `--tag` to specify the same name when the component is started. After the tag is specified, the working directory will *not be automatically deleted* when the instance is terminated, which makes it convenient to reuse the working directory.
 
-Example 1: Operate TiDB v5.3.1.
+Example 1: Operate TiDB v5.3.2.
 
 {{< copyable "shell-regular" >}}
 
 ```shell
-tiup tidb:v5.3.1
+tiup tidb:v5.3.2
 ```
 
 Example 2: Specify the tag with which TiKV operates.
@@ -218,12 +218,12 @@ The following flags are supported in this command:
 - If the version is ignored, adding `--all` means to uninstall all versions of this component.
 - If the version and the component are both ignored, adding `--all` means to uninstall all components of all versions.
 
-Example 1: Uninstall TiDB v5.3.1.
+Example 1: Uninstall TiDB v5.3.2.
 
 {{< copyable "shell-regular" >}}
 
 ```shell
-tiup uninstall tidb:v5.3.1
+tiup uninstall tidb:v5.3.2
 ```
 
 Example 2: Uninstall TiKV of all versions.

diff --git a/tiup/tiup-mirror.md b/tiup/tiup-mirror.md
@@ -76,9 +76,9 @@ The `tiup mirror clone` command provides many optional flags (might provide more
 
     If you want to clone only one version (not all versions) of a component, use `--<component>=<version>` to specify this version. For example:
 
-    - Execute the `tiup mirror clone <target-dir> --tidb v5.3.1` command to clone the v5.3.1 version of the TiDB component.
-    - Execute the `tiup mirror clone <target-dir> --tidb v5.3.1 --tikv all` command to clone the v5.3.1 version of the TiDB component and all versions of the TiKV component.
-    - Execute the `tiup mirror clone <target-dir> v5.3.1` command to clone the v5.3.1 version of all components in a cluster.
+    - Execute the `tiup mirror clone <target-dir> --tidb v5.3.2` command to clone the v5.3.2 version of the TiDB component.
+    - Execute the `tiup mirror clone <target-dir> --tidb v5.3.2 --tikv all` command to clone the v5.3.2 version of the TiDB component and all versions of the TiKV component.
+    - Execute the `tiup mirror clone <target-dir> v5.3.2` command to clone the v5.3.2 version of all components in a cluster.
 
 ## Usage examples
 

diff --git a/tiup/tiup-playground.md b/tiup/tiup-playground.md
@@ -21,7 +21,7 @@ This command actually performs the following operations:
 
 - Because this command does not specify the version of the playground component, TiUP first checks the latest version of the installed playground component. Assume that the latest version is v1.7.0, then this command works the same as `tiup playground:v1.7.0`.
 - If you have not used TiUP playground to install the TiDB, TiKV, and PD components, the playground component installs the latest stable version of these components, and then start these instances.
-- Because this command does not specify the version of the TiDB, PD, and TiKV component, TiUP playground uses the latest version of each component by default. Assume that the latest version is v5.3.1, then this command works the same as `tiup playground:v1.7.0 v5.3.1`.
+- Because this command does not specify the version of the TiDB, PD, and TiKV component, TiUP playground uses the latest version of each component by default. Assume that the latest version is v5.3.2, then this command works the same as `tiup playground:v1.7.0 v5.3.2`.
 - Because this command does not specify the number of each component, TiUP playground, by default, starts a smallest cluster that consists of one TiDB instance, one TiKV instance, one PD instance, and one TiFlash instance.
 - After starting each TiDB component, TiUP playground reminds you that the cluster is successfully started and provides you some useful information, such as how to connect to the TiDB cluster through the MySQL client and how to access the [TiDB Dashboard](/dashboard/dashboard-intro.md).