From 7b8ad3f0022aa79566027d9f60682d51ffb282a3 Mon Sep 17 00:00:00 2001 From: TomShawn <1135243111@qq.com> Date: Thu, 9 Apr 2020 20:21:14 +0800 Subject: [PATCH 1/5] how-to/upgrade: add TiUP upgrade document --- TOC.md | 3 +- .../{from-previous-version.md => ansible.md} | 8 +- how-to/upgrade/tiup.md | 221 ++++++++++++++++++ 3 files changed, 227 insertions(+), 5 deletions(-) rename how-to/upgrade/{from-previous-version.md => ansible.md} (98%) create mode 100644 how-to/upgrade/tiup.md diff --git a/TOC.md b/TOC.md index fa28813d08774..75bad406ae90c 100644 --- a/TOC.md +++ b/TOC.md @@ -91,7 +91,8 @@ - [Scale using Ansible](/how-to/scale/with-ansible.md) - [Scale a TiDB Cluster](/how-to/scale/horizontally.md) + Upgrade - - [Upgrade to the Latest Version](/how-to/upgrade/from-previous-version.md) + - [Upgrade Using TiUP (Recommended)](/how-to/upgrade/tiup.md) + - [Upgrade TiDB Ansible](/how-to/upgrade/ansible.md) - Troubleshoot - [Troubleshoot Cluster Setup](/how-to/troubleshoot/cluster-setup.md) - [Troubleshoot TiDB Lightning](/how-to/troubleshoot/tidb-lightning.md) diff --git a/how-to/upgrade/from-previous-version.md b/how-to/upgrade/ansible.md similarity index 98% rename from how-to/upgrade/from-previous-version.md rename to how-to/upgrade/ansible.md index 68efa55a07a47..919e65c666f10 100644 --- a/how-to/upgrade/from-previous-version.md +++ b/how-to/upgrade/ansible.md @@ -1,11 +1,11 @@ --- -title: TiDB Latest Development Version Upgrade Guide -summary: Learn how to upgrade to the latest development version of TiDB. +title: Upgrade TiDB Using TiDB Ansible +summary: Learn how to upgrade TiDB using TiDB Ansible. category: how-to -aliases: ['/docs/dev/how-to/upgrade/rolling-updates-with-ansible/'] +aliases: ['/docs/dev/how-to/upgrade/rolling-updates-with-ansible/','/docs/dev/how-to/upgrade/from-previous-version/'] --- -# TiDB Latest Development Version Upgrade Guide +# Upgrade TiDB Using TiDB Ansible This document is targeted for users who want to upgrade from TiDB 2.0, 2.1, 3.0, or 3.1 versions to the latest development version (`latest`), or from an earlier development version to the latest development version. The latest development version is compatible with [TiDB Binlog of the cluster version](/reference/tidb-binlog/overview.md). diff --git a/how-to/upgrade/tiup.md b/how-to/upgrade/tiup.md new file mode 100644 index 0000000000000..e92dfdecbb586 --- /dev/null +++ b/how-to/upgrade/tiup.md @@ -0,0 +1,221 @@ +--- +title: Upgrade TiDB Using TiUP +summary: Learn how to upgrade TiDB using TiUP. +category: how-to +--- + +# Upgrade TiDB Using TiUP + +This document is targeted for users who want to upgrade from TiDB 3.0 versions to TiDB 4.0 versions, or from TiDB 4.0 to a later version. + +If you have deployed the TiDB cluster using TiDB Ansible, you can use TiUP to import the TiDB Ansible configuration and perform the upgrade. + +## 1. Upgrade caveat + +- Rolling back to 3.0 versions after the update is not supported. +- To update versions earlier than 3.0 to 4.0, first update this version to 3.0 using TiDB Ansible, and use TiUP to import the TiDB Ansible configuration and update the 3.0 version to 4.0. +- After the TiDB Ansible configuration is imported into and managed by TiUP, you can no longer operate on the cluster using TiDB Ansible. Otherwise, conflicts might occur because of the inconsistent metadata. +- Currently, you cannot import the TiDB Ansible configuration if the cluster deployed using TiDB Ansible meets one of the following situations: + - The TLS encryption is enabled for the cluster. + - This is a pure key-value cluster (cluster with no TiDB instance). + - `Kafka` is enabled for the cluster. + - `Spark` is enabled for the cluster. + - `Lightning` / `Importer` is enabled for the cluster. + - You still use the `'push'` method to collect monitoring metrics (since v3.0, `pull` is the default mode, which is supported if you have not modified this mode). + - In the `inventory.ini` configuration file, the `node_exporter` or `blackbox_exporter` item of the machine is set to non-default ports through `node_exporter_port` or `blackbox_exporter_port`, which is compatible if you have unified the configuration in the `group_vars` directory. + +## 2. Install TiUP on the Control Machine + +1. Execute the following command on the Control Machine to install TiUP: + + {{< copyable "shell-regular" >}} + + ```shell + curl --proto '=https' --tlsv1.2 -sSf https://tiup-mirrors.pingcap.com/install.sh | sh + ``` + +2. Redeclare the global environment variables: + + {{< copyable "shell-regular" >}} + + ```shell + source .bash_profile + ``` + +3. Check whether TiUP is installed: + + {{< copyable "shell-regular" >}} + + ```shell + which tiup + ``` + +4. Install the TiUP cluster tool: + + {{< copyable "shell-regular" >}} + + ```shell + tiup cluster + ``` + +If you have installed TiUP before, execute the following command to update TiUP to the latest version: + +{{< copyable "shell-regular" >}} + +```shell +tiup update cluster +``` + +## 3. Import TiDB Ansible and the `inventory.ini` configuration to TiUP + +> **Note:** +> +> + If the original cluster is deployed using TiUP, you can skip this step. +> + Currently, the `inventory.ini` configuration file is identified by default. If your configuration file uses another name, specify this name. +> + Ensure that the state of the current cluster is consistent with the topology in `inventory.ini`; that components of the cluster are operating normally. Otherwise, the cluster metadata becomes abnormal after the import. + +### 3.1 Install the cluster management tool + +Use the following command to install the cluster management tool: + +{{< copyable "shell-regular" >}} + +```shell +tiup install cluster +``` + +### 3.2 Import the TiDB Ansible cluster to TiUP + +1. Execute the following command to import the TiDB Ansible cluster into TiUP (for example, in the `/home/tidb/tidb-ansible` path). Do not execute this command in the Ansible directory. + + {{< copyable "shell-regular" >}} + + ```shell + tiup cluster import -d /home/tidb/tidb-ansible + ``` + +2. After executing the above import command, if the `Inventory` information of the cluster is parsed successfully, the following prompt appears: + + {{< copyable "shell-regular" >}} + + ```shell + tiup cluster import -d /home/tidb/tidb-ansible/ + ``` + + ``` + Found inventory file /home/tidb/tidb-ansible/inventory.ini, parsing... + Found cluster "ansible-cluster" (v3.0.12), deployed with user tidb. + Prepared to import TiDB v3.0.12 cluster ansible-cluster. + Do you want to continue? [y/N]: + ``` + +3. After checking that the parsed cluster name and the version are correct, enter `y` to continue the import process. + + + If an error occurs when parsing the `Inventory` information, the import process is stopped, which does not have any impact on the original Ansible deployment method. Then you need to adjust and retry the process according to the error prompt. + + + If the original cluster name in Ansible is the same with any existing cluster name in TiUP, a warning message is returned with a new cluster name. Therefore, **do not repeatedly import the same cluster**, which results in multiple names for the same cluster in TiUP. + +After the import is complete, you can check the current cluster status by executing the `tiup cluster display ` command to verify the import result. Because the `display` command is used to query the real-time status of each node, it might take a little time to execute the command. + +### 3.3 Edit TiUP topology configuration file + +> **Note:** +> +> You can skip this step for the following situations: +> +> - The configuration parameters in the original cluster have not been modified. +> - You want to use the default parameters of `4.0` after the upgrade. + +1. Enter the `tidb-ansible / conf` configuration directory and confirm the modified parameters in the configuration template. + +2. Enter the `vi` editing mode of the topology file: + + {{< copyable "shell-regular" >}} + + ```shell + tiup cluster edit-config + ``` + +3. See the configuration template format of [topology](https://github.com/pingcap-incubator/tiops/blob/master/topology.example.yaml) and fill in the modified parameters of the original cluster in the `server_configs` section of the topology file. After the modification is completed, execute the `wq` command to save the change and exit the editing mode. Enter `Y` to confirm the change. + +> **Note:** +> +> Before upgrading to v4.0, confirm that the parameters modified in v3.0 are compatible in v4.0. See [configuration template](/reference/configuration/tikv-server/configuration-file.md) for details. + +## 4. Perform a rolling update to the TiDB cluster + +This section describes how to perform a rolling update to the TiDB cluster and how to verify the version after the update. + +### 4.1 Perform a rolling update to the TiDB cluster (to v4.0.0-rc) + +{{< copyable "shell-regular" >}} + +```shell +tiup cluster upgrade v4.0.0-rc +``` + +Performing the rolling update to the cluster will update 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 10 minutes. The instance is directly stopped after this timeout time. + +### 4.2 Verify the cluster version + +Execute the `display` command to view the latest cluster version `TiDB Version`: + +{{< copyable "shell-regular" >}} + +```shell +tiup cluster display +``` + +``` +Starting /home/tidblk/.tiup/components/cluster/v0.4.3/cluster display +TiDB Cluster: +TiDB Version: v4.0.0-rc +``` + +## 5. FAQ + +This section describes common problems encountered when updating the TiDB cluster using TiUP. + +### 5.1 If an error occurs and the updated is interrupted, how to resume the update from the point of the interruption after fixing this error? + +You can specify `--role` or `--node` to update the specified component or node. Here is the command: + +{{< copyable "shell-regular" >}} + +```shell +tiup cluster upgrade v4.0.0-rc --role tidb +``` + +or + +{{< copyable "shell-regular" >}} + +```shell +tiup cluster upgrade v4.0.0-rc --node +``` + +### 5.2 The evict leader has waited too long during the update. How to skip this step for a quick update? + +You can specify `--force`. Then the processes of transferring PD leader and evicting TiKV leader are skipped during the update. The cluster is directly restarted to update the version, which has a great impact on the cluster that runs online. Here is the command: + +{{< copyable "shell-regular" >}} + +```shell +tiup cluster upgrade v4.0.0-rc --force +``` + +### 5.3 How to update the version of tools such as pd-ctl after updating 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.0-rc`. Here is the download address: + +{{< copyable "" >}} + +``` +https://download.pingcap.org/tidb-{version}-linux-amd64.tar.gz +``` + +## 6. TiDB 4.0 compatibility changes + +- If you set the value of the `oom-action` parameter to `cancel`, when the query statement triggers the OOM threshold, the statement is killed. In v4.0, in addition to `select`, DML statements such as `insert`/`update`/`delete` might also be killed. +- TiDB v4.0 supports the length check for table names. The length limit is 64 characters. If you rename a table after the upgrade and the new name exceeds this length limit, an error is reported. v3.0 and earlier versions do not have this error reporting. +- In v4.0, the format of the `explain` execution plan is improved. Pay attention to any automatic analysis program that is customized for `explain`. From 3291832cd65ac6461b1fe76c52388e018b659757 Mon Sep 17 00:00:00 2001 From: TomShawn <1135243111@qq.com> Date: Thu, 9 Apr 2020 20:51:32 +0800 Subject: [PATCH 2/5] change titles and fix broken links --- how-to/deploy/orchestrated/ansible.md | 4 ++-- how-to/upgrade/tiup.md | 28 +++++++++++++-------------- 2 files changed, 16 insertions(+), 16 deletions(-) diff --git a/how-to/deploy/orchestrated/ansible.md b/how-to/deploy/orchestrated/ansible.md index 211ed283ff51c..fc77c11da7a62 100644 --- a/how-to/deploy/orchestrated/ansible.md +++ b/how-to/deploy/orchestrated/ansible.md @@ -20,9 +20,9 @@ You can use the TiDB Ansible configuration file to set up the cluster topology a - Deploy the whole TiDB cluster - [Start the TiDB cluster](/how-to/deploy/orchestrated/ansible-operations.md#start-a-cluster) - [Stop the TiDB cluster](/how-to/deploy/orchestrated/ansible-operations.md#stop-a-cluster) -- [Modify component configuration](/how-to/upgrade/from-previous-version.md#edit-the-configuration-file-of-tidb-cluster-components) +- [Modify component configuration](/how-to/upgrade/ansible.md#edit-the-configuration-file-of-tidb-cluster-components) - [Scale the TiDB cluster](/how-to/scale/with-ansible.md) -- [Upgrade the component version](/how-to/upgrade/from-previous-version.md#step-5-perform-a-rolling-update-to-tidb-cluster-components) +- [Upgrade the component version](/how-to/upgrade/ansible.md#step-5-perform-a-rolling-update-to-tidb-cluster-components) - [Enable the cluster binlog](/reference/tidb-binlog/overview.md) - [Clean up data of the TiDB cluster](/how-to/deploy/orchestrated/ansible-operations.md#clean-up-cluster-data) - [Destroy the TiDB cluster](/how-to/deploy/orchestrated/ansible-operations.md#destroy-a-cluster) diff --git a/how-to/upgrade/tiup.md b/how-to/upgrade/tiup.md index e92dfdecbb586..55e519fde217d 100644 --- a/how-to/upgrade/tiup.md +++ b/how-to/upgrade/tiup.md @@ -10,7 +10,7 @@ This document is targeted for users who want to upgrade from TiDB 3.0 versions t If you have deployed the TiDB cluster using TiDB Ansible, you can use TiUP to import the TiDB Ansible configuration and perform the upgrade. -## 1. Upgrade caveat +## Upgrade caveat - Rolling back to 3.0 versions after the update is not supported. - To update versions earlier than 3.0 to 4.0, first update this version to 3.0 using TiDB Ansible, and use TiUP to import the TiDB Ansible configuration and update the 3.0 version to 4.0. @@ -24,7 +24,7 @@ If you have deployed the TiDB cluster using TiDB Ansible, you can use TiUP to im - You still use the `'push'` method to collect monitoring metrics (since v3.0, `pull` is the default mode, which is supported if you have not modified this mode). - In the `inventory.ini` configuration file, the `node_exporter` or `blackbox_exporter` item of the machine is set to non-default ports through `node_exporter_port` or `blackbox_exporter_port`, which is compatible if you have unified the configuration in the `group_vars` directory. -## 2. Install TiUP on the Control Machine +## Install TiUP on the Control Machine 1. Execute the following command on the Control Machine to install TiUP: @@ -66,7 +66,7 @@ If you have installed TiUP before, execute the following command to update TiUP tiup update cluster ``` -## 3. Import TiDB Ansible and the `inventory.ini` configuration to TiUP +## Import TiDB Ansible and the `inventory.ini` configuration to TiUP > **Note:** > @@ -74,7 +74,7 @@ tiup update cluster > + Currently, the `inventory.ini` configuration file is identified by default. If your configuration file uses another name, specify this name. > + Ensure that the state of the current cluster is consistent with the topology in `inventory.ini`; that components of the cluster are operating normally. Otherwise, the cluster metadata becomes abnormal after the import. -### 3.1 Install the cluster management tool +### Install the cluster management tool Use the following command to install the cluster management tool: @@ -84,7 +84,7 @@ Use the following command to install the cluster management tool: tiup install cluster ``` -### 3.2 Import the TiDB Ansible cluster to TiUP +### Import the TiDB Ansible cluster to TiUP 1. Execute the following command to import the TiDB Ansible cluster into TiUP (for example, in the `/home/tidb/tidb-ansible` path). Do not execute this command in the Ansible directory. @@ -117,7 +117,7 @@ tiup install cluster After the import is complete, you can check the current cluster status by executing the `tiup cluster display ` command to verify the import result. Because the `display` command is used to query the real-time status of each node, it might take a little time to execute the command. -### 3.3 Edit TiUP topology configuration file +### Edit TiUP topology configuration file > **Note:** > @@ -142,11 +142,11 @@ After the import is complete, you can check the current cluster status by execut > > Before upgrading to v4.0, confirm that the parameters modified in v3.0 are compatible in v4.0. See [configuration template](/reference/configuration/tikv-server/configuration-file.md) for details. -## 4. Perform a rolling update to the TiDB cluster +## Perform a rolling update to the TiDB cluster This section describes how to perform a rolling update to the TiDB cluster and how to verify the version after the update. -### 4.1 Perform a rolling update to the TiDB cluster (to v4.0.0-rc) +### Perform a rolling update to the TiDB cluster (to v4.0.0-rc) {{< copyable "shell-regular" >}} @@ -156,7 +156,7 @@ tiup cluster upgrade v4.0.0-rc Performing the rolling update to the cluster will update 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 10 minutes. The instance is directly stopped after this timeout time. -### 4.2 Verify the cluster version +### Verify the cluster version Execute the `display` command to view the latest cluster version `TiDB Version`: @@ -172,11 +172,11 @@ TiDB Cluster: TiDB Version: v4.0.0-rc ``` -## 5. FAQ +## FAQ This section describes common problems encountered when updating the TiDB cluster using TiUP. -### 5.1 If an error occurs and the updated is interrupted, how to resume the update from the point of the interruption after fixing this error? +### If an error occurs and the updated is interrupted, how to resume the update from the point of the interruption after fixing this error? You can specify `--role` or `--node` to update the specified component or node. Here is the command: @@ -194,7 +194,7 @@ or tiup cluster upgrade v4.0.0-rc --node ``` -### 5.2 The evict leader has waited too long during the update. How to skip this step for a quick update? +### The evict leader has waited too long during the update. How to skip this step for a quick update? You can specify `--force`. Then the processes of transferring PD leader and evicting TiKV leader are skipped during the update. The cluster is directly restarted to update the version, which has a great impact on the cluster that runs online. Here is the command: @@ -204,7 +204,7 @@ You can specify `--force`. Then the processes of transferring PD leader and evic tiup cluster upgrade v4.0.0-rc --force ``` -### 5.3 How to update the version of tools such as pd-ctl after updating the TiDB cluster? +### How to update the version of tools such as pd-ctl after updating 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.0-rc`. Here is the download address: @@ -214,7 +214,7 @@ Currently, TiUP does not update and manage the version of tools. If you need the https://download.pingcap.org/tidb-{version}-linux-amd64.tar.gz ``` -## 6. TiDB 4.0 compatibility changes +## TiDB 4.0 compatibility changes - If you set the value of the `oom-action` parameter to `cancel`, when the query statement triggers the OOM threshold, the statement is killed. In v4.0, in addition to `select`, DML statements such as `insert`/`update`/`delete` might also be killed. - TiDB v4.0 supports the length check for table names. The length limit is 64 characters. If you rename a table after the upgrade and the new name exceeds this length limit, an error is reported. v3.0 and earlier versions do not have this error reporting. From e08892279e9f6a5f7b88f011dad4626f73a06d1d Mon Sep 17 00:00:00 2001 From: TomShawn <1135243111@qq.com> Date: Fri, 10 Apr 2020 10:48:40 +0800 Subject: [PATCH 3/5] align #2693 --- TOC.md | 4 ++-- how-to/deploy/orchestrated/ansible.md | 4 ++-- .../{ansible.md => from-previous-version.md} | 0 how-to/upgrade/{tiup.md => using-tiup.md} | 16 +++++----------- 4 files changed, 9 insertions(+), 15 deletions(-) rename how-to/upgrade/{ansible.md => from-previous-version.md} (100%) rename how-to/upgrade/{tiup.md => using-tiup.md} (95%) diff --git a/TOC.md b/TOC.md index 47b1ef47cb763..ef2e6dfbb7b24 100644 --- a/TOC.md +++ b/TOC.md @@ -91,8 +91,8 @@ - [Scale using Ansible](/how-to/scale/with-ansible.md) - [Scale a TiDB Cluster](/how-to/scale/horizontally.md) + Upgrade - - [Upgrade Using TiUP (Recommended)](/how-to/upgrade/tiup.md) - - [Upgrade TiDB Ansible](/how-to/upgrade/ansible.md) + - [Upgrade Using TiUP (Recommended)](/how-to/upgrade/using-tiup.md) + - [Upgrade TiDB Ansible](/how-to/upgrade/from-previous-version.md) - Troubleshoot - [Troubleshoot Cluster Setup](/how-to/troubleshoot/cluster-setup.md) - [Troubleshoot TiDB Lightning](/how-to/troubleshoot/tidb-lightning.md) diff --git a/how-to/deploy/orchestrated/ansible.md b/how-to/deploy/orchestrated/ansible.md index fc77c11da7a62..211ed283ff51c 100644 --- a/how-to/deploy/orchestrated/ansible.md +++ b/how-to/deploy/orchestrated/ansible.md @@ -20,9 +20,9 @@ You can use the TiDB Ansible configuration file to set up the cluster topology a - Deploy the whole TiDB cluster - [Start the TiDB cluster](/how-to/deploy/orchestrated/ansible-operations.md#start-a-cluster) - [Stop the TiDB cluster](/how-to/deploy/orchestrated/ansible-operations.md#stop-a-cluster) -- [Modify component configuration](/how-to/upgrade/ansible.md#edit-the-configuration-file-of-tidb-cluster-components) +- [Modify component configuration](/how-to/upgrade/from-previous-version.md#edit-the-configuration-file-of-tidb-cluster-components) - [Scale the TiDB cluster](/how-to/scale/with-ansible.md) -- [Upgrade the component version](/how-to/upgrade/ansible.md#step-5-perform-a-rolling-update-to-tidb-cluster-components) +- [Upgrade the component version](/how-to/upgrade/from-previous-version.md#step-5-perform-a-rolling-update-to-tidb-cluster-components) - [Enable the cluster binlog](/reference/tidb-binlog/overview.md) - [Clean up data of the TiDB cluster](/how-to/deploy/orchestrated/ansible-operations.md#clean-up-cluster-data) - [Destroy the TiDB cluster](/how-to/deploy/orchestrated/ansible-operations.md#destroy-a-cluster) diff --git a/how-to/upgrade/ansible.md b/how-to/upgrade/from-previous-version.md similarity index 100% rename from how-to/upgrade/ansible.md rename to how-to/upgrade/from-previous-version.md diff --git a/how-to/upgrade/tiup.md b/how-to/upgrade/using-tiup.md similarity index 95% rename from how-to/upgrade/tiup.md rename to how-to/upgrade/using-tiup.md index 55e519fde217d..bf7299f0b553f 100644 --- a/how-to/upgrade/tiup.md +++ b/how-to/upgrade/using-tiup.md @@ -74,16 +74,6 @@ tiup update cluster > + Currently, the `inventory.ini` configuration file is identified by default. If your configuration file uses another name, specify this name. > + Ensure that the state of the current cluster is consistent with the topology in `inventory.ini`; that components of the cluster are operating normally. Otherwise, the cluster metadata becomes abnormal after the import. -### Install the cluster management tool - -Use the following command to install the cluster management tool: - -{{< copyable "shell-regular" >}} - -```shell -tiup install cluster -``` - ### Import the TiDB Ansible cluster to TiUP 1. Execute the following command to import the TiDB Ansible cluster into TiUP (for example, in the `/home/tidb/tidb-ansible` path). Do not execute this command in the Ansible directory. @@ -136,7 +126,11 @@ After the import is complete, you can check the current cluster status by execut tiup cluster edit-config ``` -3. See the configuration template format of [topology](https://github.com/pingcap-incubator/tiops/blob/master/topology.example.yaml) and fill in the modified parameters of the original cluster in the `server_configs` section of the topology file. After the modification is completed, execute the `wq` command to save the change and exit the editing mode. Enter `Y` to confirm the change. +3. See the configuration template format of [topology](https://github.com/pingcap-incubator/tiops/blob/master/topology.example.yaml) and fill in the modified parameters of the original cluster in the `server_configs` section of the topology file. + + Even if the label has been configured for the cluster, you also need to fill in the label in the configuration according to the format in the template. In later versions, the label will be automatically imported. + + After the modification is completed, execute the `wq` command to save the change and exit the editing mode. Enter `Y` to confirm the change. > **Note:** > From 19774c740fe0db8c2daccd0d264739cd67e4093a Mon Sep 17 00:00:00 2001 From: TomShawn <1135243111@qq.com> Date: Fri, 10 Apr 2020 10:50:02 +0800 Subject: [PATCH 4/5] remove alias --- how-to/upgrade/from-previous-version.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/how-to/upgrade/from-previous-version.md b/how-to/upgrade/from-previous-version.md index 919e65c666f10..fe75273987a4b 100644 --- a/how-to/upgrade/from-previous-version.md +++ b/how-to/upgrade/from-previous-version.md @@ -2,7 +2,7 @@ title: Upgrade TiDB Using TiDB Ansible summary: Learn how to upgrade TiDB using TiDB Ansible. category: how-to -aliases: ['/docs/dev/how-to/upgrade/rolling-updates-with-ansible/','/docs/dev/how-to/upgrade/from-previous-version/'] +aliases: ['/docs/dev/how-to/upgrade/rolling-updates-with-ansible/'] --- # Upgrade TiDB Using TiDB Ansible From 00f49a81f1916d13dc8874899db9ea9d0b37cacf Mon Sep 17 00:00:00 2001 From: TomShawn <41534398+TomShawn@users.noreply.github.com> Date: Fri, 10 Apr 2020 17:09:55 +0800 Subject: [PATCH 5/5] Update TOC.md Co-Authored-By: Keke Yi <40977455+yikeke@users.noreply.github.com> --- TOC.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TOC.md b/TOC.md index ef2e6dfbb7b24..d3377fdedcaca 100644 --- a/TOC.md +++ b/TOC.md @@ -92,7 +92,7 @@ - [Scale a TiDB Cluster](/how-to/scale/horizontally.md) + Upgrade - [Upgrade Using TiUP (Recommended)](/how-to/upgrade/using-tiup.md) - - [Upgrade TiDB Ansible](/how-to/upgrade/from-previous-version.md) + - [Upgrade Using TiDB Ansible](/how-to/upgrade/from-previous-version.md) - Troubleshoot - [Troubleshoot Cluster Setup](/how-to/troubleshoot/cluster-setup.md) - [Troubleshoot TiDB Lightning](/how-to/troubleshoot/tidb-lightning.md)