Tidb upgrade version

One 、 Introduction to the environment

current version ：4.0.15
Upgraded version ：5.3.1

Two 、 Operation steps

1. upgrade tiup edition

tiup update --self
tiup --version

2. upgrade tiup cluster edition

tiup update cluster
tiup cluster --version

3. Preparation for offline deployment （ This step can be skipped for non offline deployment ）

3.1 Update offline image

tar xzvf tidb-community-server-${version}-linux-amd64.tar.gz
sh tidb-community-server-${version}-linux-amd64/local_install.sh
source /home/tidb/.bash_profile

3.2 upgrade cluster Components

tiup update cluster

The offline image has been updated successfully . If it is found that TiUP Operation error reporting , May be manifest Not updated , Try rm -rf ~/.tiup/manifests/* Reuse later .

4. Edit the configuration to ensure compatibility

tiup cluster edit-config <cluster-name>

4.1 tidb5.3 Parameters whose version has been discarded

pessimistic-txn.enabled
server.request-batch-enable-cross-command
server.request-batch-wait-duration

Configuration file parameter address ：

• tikv
• tidb
• pd
• tiflash

4.2 Check cluster health

tiup cluster check <cluster-name> --cluster

5. Upgrade cluster

5.1 Upgrade without downtime

tiup cluster upgrade <cluster-name> <version>

Be careful ：

• Rolling upgrade will upgrade all components one by one . upgrade TiKV period , Will one by one TiKV All the leader Cut away and then stop TiKV example . The default timeout is 5 minute （300 second ）, The instance will be stopped directly after the timeout .
• Use --force Parameters can be used without expelling leader To quickly upgrade the cluster to the new version , But this method will ignore all errors in the upgrade , No valid prompt after the upgrade fails , Please use with caution .
• If you want to keep performance stable , You need to guarantee TiKV All the leader After the deportation is completed, the TiKV example , You can specify --transfer-timeout For a larger value , Such as --transfer-timeout 3600, The unit is in seconds .
• from 5.3 Upgrade the previous version to 5.3 And later versions , Online upgrade is not supported TiFlash, Only the first TiFlash Instance close , Then upgrade the cluster offline , Last reload Entire cluster , Guaranteed addition TiFlash Other components are upgraded without downtime .

5.2 Stop and upgrade

5.2.1 Stop the cluster

tiup cluster stop <cluster-name>

5.2.2 Stop and upgrade

tiup cluster upgrade <cluster-name> <version> --offline

5.2.3 Start cluster

tiup cluster start <cluster-name>

3、 ... and 、 Error handling

1. Use tiup cluster audit Command to view operation records ：

tiup cluster audit
#  Find the failed upgrade operation record , And make a note of  ID, In the next step, you will use  <audit-id>  Indicates the operation record  ID  Value .

2. Use tiup cluster replay Command to retry the corresponding operation ：

tiup cluster replay <audit-id>

Official website address ： Official document