From bb71e42b619d4b072e6988096a36a3a10b510e2f Mon Sep 17 00:00:00 2001 From: TomShawn <41534398+TomShawn@users.noreply.github.com> Date: Thu, 10 Jun 2021 11:38:14 +0800 Subject: [PATCH] bump version --- download-ecosystem-tools.md | 10 +++++----- pd-recover.md | 2 +- production-deployment-using-tiup.md | 6 +++--- quick-start-with-tidb.md | 8 ++++---- scale-tidb-using-tiup.md | 2 +- ticdc/manage-ticdc.md | 4 ++-- tiup/tiup-component-cluster-deploy.md | 2 +- upgrade-tidb-using-tiup.md | 8 ++++---- 8 files changed, 21 insertions(+), 21 deletions(-) diff --git a/download-ecosystem-tools.md b/download-ecosystem-tools.md index 9fe98da24c3c9..de438add13ae6 100644 --- a/download-ecosystem-tools.md +++ b/download-ecosystem-tools.md @@ -17,7 +17,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.0.0` is `https://download.pingcap.org/tidb-v5.0.0-linux-amd64.tar.gz`. +> `{version}` in the above download link indicates the version number of TiDB. For example, the download link for `v5.0.2` is `https://download.pingcap.org/tidb-v5.0.2-linux-amd64.tar.gz`. ## TiDB Lightning @@ -29,7 +29,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.0.0` is `https://download.pingcap.org/tidb-toolkit-v5.0.0-linux-amd64.tar.gz`. +> `{version}` in the above download link indicates the version number of TiDB Lightning. For example, the download link for `v5.0.2` is `https://download.pingcap.org/tidb-toolkit-v5.0.2-linux-amd64.tar.gz`. ## BR (backup and restore) @@ -41,7 +41,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.0.0-beta` is `http://download.pingcap.org/tidb-toolkit-v5.0.0-beta-linux-amd64.tar.gz`. +> `{version}` in the above download link indicates the version number of BR. For example, the download link for `v5.0.2` is `http://download.pingcap.org/tidb-toolkit-v5.0.2-linux-amd64.tar.gz`. ## TiDB DM (Data Migration) @@ -53,7 +53,7 @@ Download [DM](https://docs.pingcap.com/tidb-data-migration/v1.0/overview) by usi > **Note:** > -> `{version}` in the above download link indicates the version number of DM. For example, the download link for `v2.0.1` is `https://download.pingcap.org/dm-v2.0.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 `v2.0.3` is `https://download.pingcap.org/dm-v2.0.3-linux-amd64.tar.gz`. You can check the published DM versions in the [DM Release](https://github.com/pingcap/dm/releases) page. ## Dumpling @@ -65,7 +65,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.11` version of Dumpling is `https://download.pingcap.org/tidb-toolkit-v4.0.11-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 `v5.0.2` version of Dumpling is `https://download.pingcap.org/tidb-toolkit-v5.0.2-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 index 3286a5e19058e..94107ac4c3cb8 100644 --- 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.0.0`, the package download link is `https://download.pingcap.org/tidb-v5.0.0-linux-amd64.tar.gz`. +> `{version}` indicates the version number of TiDB. For example, if `{version}` is `v5.0.2`, the package download link is `https://download.pingcap.org/tidb-v5.0.2-linux-amd64.tar.gz`. ## Quick Start diff --git a/production-deployment-using-tiup.md b/production-deployment-using-tiup.md index 1baf76582ca4b..b7615326f2774 100644 --- a/production-deployment-using-tiup.md +++ b/production-deployment-using-tiup.md @@ -260,13 +260,13 @@ Then execute the `deploy` command to deploy the TiDB cluster: {{< copyable "shell-regular" >}} ```shell -tiup cluster deploy tidb-test v5.0.0 ./topology.yaml --user root [-p] [-i /home/root/.ssh/gcp_rsa] +tiup cluster deploy tidb-test v5.0.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.0.0` as an example. +- You can see the latest supported versions by running `tiup list tidb`. This document takes `v5.0.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. @@ -288,7 +288,7 @@ TiUP supports managing multiple TiDB clusters. The command above outputs informa Starting /home/tidb/.tiup/components/cluster/v1.3.0/cluster list Name User Version Path PrivateKey ---- ---- ------- ---- ---------- -tidb-test tidb v5.0.0 /home/tidb/.tiup/storage/cluster/clusters/tidb-test /home/tidb/.tiup/storage/cluster/clusters/tidb-test/ssh/id_rsa +tidb-test tidb v5.0.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 index 4f8b9bfd30f9e..70ac48c806f97 100644 --- a/quick-start-with-tidb.md +++ b/quick-start-with-tidb.md @@ -55,10 +55,10 @@ As a distributed system, a basic TiDB test cluster usually consists of 2 TiDB in {{< copyable "shell-regular" >}} ```shell - tiup playground v5.0.1 --db 2 --pd 3 --kv 3 --monitor + tiup playground v5.0.2 --db 2 --pd 3 --kv 3 --monitor ``` - The command downloads a version cluster to the local machine and starts it, such as v5.0.1. `--monitor` means that the monitoring component is also deployed. + The command downloads a version cluster to the local machine and starts it, such as v5.0.2. `--monitor` means that the monitoring component is also deployed. To view the latest version, run `tiup list tidb`. @@ -160,10 +160,10 @@ As a distributed system, a basic TiDB test cluster usually consists of 2 TiDB in {{< copyable "shell-regular" >}} ```shell - tiup playground v5.0.1 --db 2 --pd 3 --kv 3 --monitor + tiup playground v5.0.2 --db 2 --pd 3 --kv 3 --monitor ``` - The command downloads a version cluster to the local machine and starts it, such as v5.0.1. `--monitor` means that the monitoring component is also deployed. + The command downloads a version cluster to the local machine and starts it, such as v5.0.2. `--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 index 9791c26d17081..564503c0ed1eb 100644 --- a/scale-tidb-using-tiup.md +++ b/scale-tidb-using-tiup.md @@ -257,7 +257,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.3.0/cluster display TiDB Cluster: - TiDB Version: v5.0.0 + TiDB Version: v5.0.2 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 index b026750b5e96f..4da8af0a7ab4d 100644 --- a/ticdc/manage-ticdc.md +++ b/ticdc/manage-ticdc.md @@ -9,14 +9,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.6. +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.0.2. {{< copyable "shell-regular" >}} ```shell tiup update --self && \ tiup update --all && \ -tiup cluster upgrade v4.0.6 +tiup cluster upgrade v5.0.2 ``` ### Notes for upgrade diff --git a/tiup/tiup-component-cluster-deploy.md b/tiup/tiup-component-cluster-deploy.md index 58b98d42ac150..2d87a85d37de6 100644 --- a/tiup/tiup-component-cluster-deploy.md +++ b/tiup/tiup-component-cluster-deploy.md @@ -13,7 +13,7 @@ tiup cluster deploy [flags] ``` - ``: the name of the new cluster, which cannot be the same as the existing cluster names. -- ``: the version number of the TiDB cluster to deploy, such as `v4.0.9`. +- ``: the version number of the TiDB cluster to deploy, such as `v5.0.2`. - ``: 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 index 9a772a891fb8c..41e2396dff4c6 100644 --- a/upgrade-tidb-using-tiup.md +++ b/upgrade-tidb-using-tiup.md @@ -149,12 +149,12 @@ If your application has a maintenance window for the database to be stopped for tiup cluster upgrade ``` -For example, if you want to upgrade the cluster to v5.0.0: +For example, if you want to upgrade the cluster to v5.0.2: {{< copyable "shell-regular" >}} ```shell -tiup cluster upgrade v5.0.0 +tiup cluster upgrade v5.0.2 ``` > **Note:** @@ -204,7 +204,7 @@ tiup cluster display ``` Cluster type: tidb Cluster name: -Cluster version: v5.0.0 +Cluster version: v5.0.2 ``` > **Note:** @@ -254,7 +254,7 @@ You can upgrade the tool version by using TiUP to install the `ctl` component of {{< copyable "shell-regular" >}} ```shell -tiup install ctl:v5.0.0 +tiup install ctl:v5.0.2 ``` ## TiDB 5.0 compatibility changes