Native Era: Portable, Scalable, Automated Full lifecycle management of TiDB cluster - Deployment - Upgrading - Scaling - Handle network, hardware failures, etc. - Backup/Restore/Data migration - ... management of a TiDB Cluster - Deploying - Bootstrapping - Configure services/configmaps, etc. - Upgrading - Change version, config, etc. - Scaling - Automatic Failover - Create replacements for failed replicas pd-server --initial=pd3 TiDB Discovery pd-server --join=pd3 pd-server --join=pd3,pd2 PingCAP.com Upgrading It’s ok to upgrade a High Availability system like TiDB directly. But, to avoid spikes we use StatefulSet

changes you need to know when you up- grade from v8.3.0 to the current version (v8.4.0). If you are upgrading from v8.2.0 or earlier versions to the current version, you might also need to check the compatibility gz 78 • binlogctl • arbiter 2.2.4 Operating system and platform requirement changes Before upgrading TiDB, ensure that your operating system version meets the OS and platform requirements. • According starting from the 8.4 DMR version. It is recommended to use Rocky Linux 9.1 or a later version. Upgrading a TiDB cluster on CentOS 7 to v8.4.0 or later will cause the cluster to become unavailable. • According

SQL • Support upgrading SELECT LOCK IN SHARE MODE to exclusive locks #54999 @cfzjywxk TiDB does not support SELECT LOCK IN SHARE MODE yet. Starting from v8.3.0, TiDB supports upgrading SELECT LOCK IN changes you need to know when you up- grade from v8.2.0 to the current version (v8.3.0). If you are upgrading from v8.1.0 or earlier versions to the current version, you might also need to check the compatibility @Defined2014 • Fix the issue that SHOW IMPORT JOBS reports an error Unknown column ' �→ summary' after upgrading from v7.1 #54241 @tangenta • Fix the issue that obtaining the column information using information_schema

changes you need to know when you up- grade from v8.3.0 to the current version (v8.4.0). If you are upgrading from v8.2.0 or earlier versions to the current version, you might also need to check the compatibility 600 PROPAGATION_NESTED behavior. It is recommended to upgrade to v6.2.0 or a later version. If upgrading TiDB is not possible, and your applications are based on the Java Spring framework that uses the Oracle Enterprise Linux. • Support for Ubuntu 16.04 will be removed in future versions of TiDB. Upgrading to Ubuntu 18.04 or later is strongly recommended. • CentOS Stream 8 reaches End of Builds on May

configuration change remains compatible with earlier versions. For existing TiDB clusters, when upgrading to TiDB v7.6.0 or a later version, the Titan engine is disabled by default. You have the flexibility changes you need to know when you up- grade from v7.5.0 to the current version (v7.6.0). If you are upgrading from v7.4.0 or earlier versions to the current version, you might also need to check the compatibility adding index fails for DDL statements due to out of memory #47862 @GMHDBJD • Fix the issue that upgrading the cluster during executing ADD INDEX might cause the data to be inconsistent with the indexes

tection of system resources. To maintain compatibility, the original behavior is retained when upgrading from earlier versions to v8.2.0 or later versions. To enable the enhanced privilege control, set changes you need to know when you up- grade from v8.1.0 to the current version (v8.2.0). If you are upgrading from v8.0.0 or earlier versions to the current version, you might also need to check the compatibility environment #11219 @lidezhu • TiDB Data Migration (DM) • Fix the connection blocking issue by upgrading go-mysql #11041 @D3Hunter • Fix the issue that SET statements cause DM to panic during the migration

changes you need to know when you up- grade from v8.0.0 to the current version (v8.1.0). If you are upgrading from v7.6.0 or earlier versions to the current version, you might also need to check the compatibility Fix the issue that TiFlash metadata might become corrupted and cause the pro- cess to panic when upgrading a cluster from a version earlier than v6.5.0 to v6.5.0 or later #9039 @JaySon-Huang • Fix the issue 511 PROPAGATION_NESTED behavior. It is recommended to upgrade to v6.2.0 or a later version. If upgrading TiDB is not possible, and your applications are based on the Java Spring framework that uses the

changes you need to know when you up- grade from v7.4.0 to the current version (v7.5.0). If you are upgrading from v7.3.0 or earlier versions to the current version, you might also need to check the compatibility Oracle Enterprise Linux. • Support for Ubuntu 16.04 will be removed in future versions of TiDB. Upgrading to Ubuntu 18.04 or later is strongly recommended. • If you are using the 32-bit version of an operating the CentOS organization. • Support for Ubuntu 16.04 will be removed in future versions of TiDB. Upgrading to Ubuntu 18.04 or later is strongly recommended. • If you are using the 32-bit version of an operating

changes you need to know when you up- grade from v8.0.0 to the current version (v8.1.0). If you are upgrading from v7.6.0 or earlier versions to the current version, you might also need to check the compatibility Fix the issue that TiFlash metadata might become corrupted and cause the pro- cess to panic when upgrading a cluster from a version earlier than v6.5.0 to v6.5.0 or later #9039 @JaySon-Huang • Fix the issue Oracle Enterprise Linux. • Support for Ubuntu 16.04 will be removed in future versions of TiDB. Upgrading to Ubuntu 18.04 or later is strongly recommended. • If you are using the 32-bit version of an operating

changes you need to know when you up- grade from v7.6.0 to the current version (v8.0.0). If you are upgrading from v7.5.0 or earlier versions to the current version, you might also need to check the compatibility the CentOS organization. • Support for Ubuntu 16.04 will be removed in future versions of TiDB. Upgrading to Ubuntu 18.04 or later is strongly recommended. • If you are using the 32-bit version of an operating perform daily database operations, including deploying, starting, stopping, destroying, scaling, and upgrading a TiDB cluster, and manage TiDB cluster parameters. TiUP supports deploying TiDB, TiFlash, TiDB