Bump version for v4.0.14 (#6040)

pingcap · Jul 28, 2021 · b7e1579 · b7e1579
1 parent 2fa07a5
commit b7e1579
Show file tree

Hide file tree

Showing 9 changed files with 21 additions and 21 deletions.
diff --git a/download-ecosystem-tools.md b/download-ecosystem-tools.md
@@ -18,7 +18,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 `v4.0.13` is `https://download.pingcap.org/tidb-v4.0.13-linux-amd64.tar.gz`.
+> `{version}` in the above download link indicates the version number of TiDB. For example, the download link for `v4.0.14` is `https://download.pingcap.org/tidb-v4.0.14-linux-amd64.tar.gz`.
 
 ## TiDB Lightning
 
@@ -30,7 +30,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 `v4.0.13` is `https://download.pingcap.org/tidb-toolkit-v4.0.13-linux-amd64.tar.gz`.
+> `{version}` in the above download link indicates the version number of TiDB Lightning. For example, the download link for `v4.0.14` is `https://download.pingcap.org/tidb-toolkit-v4.0.14-linux-amd64.tar.gz`.
 
 ## BR (backup and restore)
 
@@ -42,7 +42,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 `v4.0.13` is `http://download.pingcap.org/tidb-toolkit-v4.0.13-linux-amd64.tar.gz`.
+> `{version}` in the above download link indicates the version number of BR. For example, the download link for `v4.0.14` is `http://download.pingcap.org/tidb-toolkit-v4.0.14-linux-amd64.tar.gz`.
 
 ## TiDB DM (Data Migration)
 
@@ -66,7 +66,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 `v4.0.13` version of Dumpling is `https://download.pingcap.org/tidb-toolkit-v4.0.13-linux-amd64.tar.gz`. You can view the currently released versions in [Dumpling Releases](https://github.com/pingcap/dumpling/releases).
+> The `{version}` in the download link is the version number of Dumpling. For example, the link for downloading the `v4.0.14` version of Dumpling is `https://download.pingcap.org/tidb-toolkit-v4.0.14-linux-amd64.tar.gz`. You can view the currently released versions in [Dumpling Releases](https://github.com/pingcap/dumpling/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-recover.md b/pd-recover.md
@@ -27,7 +27,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 `v4.0.13`, the package download link is `https://download.pingcap.org/tidb-v4.0.13-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`.
+> `{version}` indicates the version number of TiDB. For example, if `{version}` is `v4.0.14`, the package download link is `https://download.pingcap.org/tidb-v4.0.14-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`.
 
 ## Quick Start
 

diff --git a/production-deployment-using-tiup.md b/production-deployment-using-tiup.md
@@ -134,13 +134,13 @@ The following topology documents provide a cluster configuration template for ea
 {{< copyable "shell-regular" >}}
 
 ```shell
-tiup cluster deploy tidb-test v4.0.13 ./topology.yaml --user root [-p] [-i /home/root/.ssh/gcp_rsa]
+tiup cluster deploy tidb-test v4.0.14 ./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`.
-- The version of the TiDB cluster is `v4.0.13`. You can see other supported versions by running `tiup list tidb`.
+- The version of the TiDB cluster is `v4.0.14`. You can see other supported versions by running `tiup list tidb`.
 - 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.
@@ -162,7 +162,7 @@ TiUP supports managing multiple TiDB clusters. The command above outputs informa
 Starting /home/tidb/.tiup/components/cluster/v1.0.0/cluster list
 Name              User  Version        Path                                                        PrivateKey
 ----              ----  -------        ----                                                        ----------
-tidb-test         tidb  v4.0.13      /home/tidb/.tiup/storage/cluster/clusters/tidb-test         /home/tidb/.tiup/storage/cluster/clusters/tidb-test/ssh/id_rsa
+tidb-test         tidb  v4.0.14      /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/production-offline-deployment-using-tiup.md b/production-offline-deployment-using-tiup.md
@@ -239,14 +239,14 @@ Execute the following command to deploy the TiDB cluster:
 {{< copyable "shell-regular" >}}
 
 ```bash
-tiup cluster deploy tidb-test v4.0.13 topology.yaml --user tidb [-p] [-i /home/root/.ssh/gcp_rsa]
+tiup cluster deploy tidb-test v4.0.14 topology.yaml --user tidb [-p] [-i /home/root/.ssh/gcp_rsa]
 tiup cluster start tidb-test
 ```
 
 > **Parameter description:**
 >
 > - The name of the cluster deployed by the TiUP cluster is `tidb-test`.
-> - The deployment version is `v4.0.13`. To obtain other supported versions, run `tiup list tidb`.
+> - The deployment version is `v4.0.14`. To obtain other supported versions, run `tiup list tidb`.
 > - The initialization configuration file is `topology.yaml`.
 > - `–user tidb`: log in to the target machine using the `tidb` user account to complete the cluster deployment. The `tidb` user needs to have `ssh` and `sudo` privileges of the target machine. 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.

diff --git a/quick-start-with-tidb.md b/quick-start-with-tidb.md
@@ -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 v4.0.13 --db 2 --pd 3 --kv 3 --monitor
+        tiup playground v4.0.14 --db 2 --pd 3 --kv 3 --monitor
         ```
 
-        The command downloads a version cluster to the local machine and starts it，such as v4.0.13. `--monitor` means that the monitoring component is also deployed.
+        The command downloads a version cluster to the local machine and starts it，such as v4.0.14. `--monitor` means that the monitoring component is also deployed.
 
         To view the latest version, run `tiup list tidb`.
 

diff --git a/scale-tidb-using-tiup.md b/scale-tidb-using-tiup.md
@@ -258,7 +258,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/v0.4.6/cluster display <cluster-name>
     TiDB Cluster: <cluster-name>
-    TiDB Version: v4.0.13
+    TiDB Version: v4.0.14
     ID              Role         Host        Ports                            Status  Data Dir                Deploy Dir
     --              ----         ----        -----                            ------  --------                ----------
     10.0.1.3:8300   cdc          10.0.1.3    8300                             Up      -                       deploy/cdc-8300

diff --git a/ticdc/manage-ticdc.md b/ticdc/manage-ticdc.md
@@ -10,14 +10,14 @@ This document describes how to manage the TiCDC cluster and replication tasks us
 
 ## 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 v4.0.13.
+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 v4.0.14.
 
 {{< copyable "shell-regular" >}}
 
 ```shell
 tiup update --self && \
 tiup update --all && \
-tiup cluster upgrade <cluster-name> v4.0.13
+tiup cluster upgrade <cluster-name> v4.0.14
 ```
 
 ### Notes for upgrade

diff --git a/tiup/tiup-component-cluster-deploy.md b/tiup/tiup-component-cluster-deploy.md
@@ -13,7 +13,7 @@ tiup cluster deploy <cluster-name> <version> <topology.yaml> [flags]
 ```
 
 - `<cluster-name>`: the name of the new cluster, which cannot be the same as the existing cluster names.
-- `<version>`: the version number of the TiDB cluster to deploy, such as `v4.0.13`.
+- `<version>`: the version number of the TiDB cluster to deploy, such as `v4.0.14`.
 - `<topology.yaml>`: the prepared [topology file](/tiup/tiup-cluster-topology-reference.md).
 
 ## Options

diff --git a/upgrade-tidb-using-tiup.md b/upgrade-tidb-using-tiup.md
@@ -174,12 +174,12 @@ This section describes how to perform a rolling upgrade to the TiDB cluster and
 tiup cluster upgrade <cluster-name> <version>
 ```
 
-For example, if you want to upgrade the cluster to v4.0.13:
+For example, if you want to upgrade the cluster to v4.0.14:
 
 {{< copyable "shell-regular" >}}
 
 ```shell
-tiup cluster upgrade <cluster-name> v4.0.13
+tiup cluster upgrade <cluster-name> v4.0.14
 ```
 
 Performing a rolling upgrade to the cluster will upgrade all components one by one. During the upgrade of TiKV, all leaders in a TiKV instance are evicted before stopping the instance. The default timeout time is 5 minutes. The instance is directly stopped after this timeout time.
@@ -201,7 +201,7 @@ tiup cluster display <cluster-name>
 ```
 Starting /home/tidblk/.tiup/components/cluster/v1.0.0/cluster display <cluster-name>
 TiDB Cluster: <cluster-name>
-TiDB Version: v4.0.13
+TiDB Version: v4.0.14
 ```
 
 > **Note:**
@@ -223,12 +223,12 @@ You can specify `--force`. Then the processes of transferring PD leader and evic
 {{< copyable "shell-regular" >}}
 
 ```shell
-tiup cluster upgrade <cluster-name> v4.0.13 --force
+tiup cluster upgrade <cluster-name> v4.0.14 --force
 ```
 
 ### How to update the version of tools such as pd-ctl after upgrading the TiDB cluster?
 
-Currently, TiUP does not update and manage the version of tools. If you need the tool package of the latest version, directly download the TiDB package and replace `{version}` with the corresponding version such as `v4.0.13`. Here is the download address:
+Currently, TiUP does not update and manage the version of tools. If you need the tool package of the latest version, directly download the TiDB package and replace `{version}` with the corresponding version such as `v4.0.14`. Here is the download address:
 
 {{< copyable "" >}}