Portable, Scalable, Automated Full lifecycle management of TiDB cluster - Deployment - Upgrading - Scaling - Handle network, hardware failures, etc. - Backup/Restore/Data migration - ... TiDB Operator Bootstrapping - Configure services/configmaps, etc. - Upgrading - Change version, config, etc. - Scaling - Automatic Failover - Create replacements for failed replicas PingCAP.com Deploying - Bootstrapping successfully, scale in the StatefulSet Scaling In - PD PingCAP.com - Delete the TiKV store via PD API first - Wait for the store to be tombstoned - Scale the statefulset Scaling In - TiKV PingCAP.com - Scale

target server while the scaling is in progress, and make sure you finish uploading before the scaling ends. Otherwise an error will occur. If an error occurs during scaling, you can perform the following to reinstall the plug-in. 1. Scale out the cluster again. 2. Upload the plug-in file after the scaling is completed. 3. Run the `tiup cluster start cluster_name command` to restart the cluster. Upgrade

Easy horizontal scaling The TiDB architecture design separates computing from storage, letting you scale out or scale in the computing or storage capacity online as needed. The scaling process is transparent cost-effective solution that adopts a separate comput- ing and storage architecture, enabling easy scaling of computing or storage capacity separately. The computing layer supports a maximum of 512 nodes manage and maintain connections to TiDB so that they live �→ through rolling restarts, upgrades, or scaling events. �→ Data

Easy horizontal scaling The TiDB architecture design separates computing from storage, letting you scale out or scale in the computing or storage capacity online as needed. The scaling process is transparent cost-effective solution that adopts a separate comput- ing and storage architecture, enabling easy scaling of computing or storage capacity separately. The computing layer supports a maximum of 512 nodes scenarios: • Verify TiDB version upgrades 48 • Assess change impact • Validate performance before scaling TiDB • Test performance limits For more information, see documentation. 2.2.1.4 SQL • Support

Easy horizontal scaling The TiDB architecture design separates computing from storage, letting you scale out or scale in the computing or storage capacity online as needed. The scaling process is transparent cost-effective solution that adopts a separate comput- ing and storage architecture, enabling easy scaling of computing or storage capacity separately. The computing layer supports a maximum of 512 nodes to reduce latency, improve throughput, and avoid slow loading of statistics that affect business scaling. Adaptive concurrent loading is now supported. By default, the configuration item stats-load-concurrency

Easy horizontal scaling The TiDB architecture design separates computing from storage, letting you scale out or scale in the computing or storage capacity online as needed. The scaling process is transparent cost-effective solution that adopts a separate comput- ing and storage architecture, enabling easy scaling of computing or storage capacity separately. The computing layer supports a maximum of 512 nodes scenarios: • Verify TiDB version upgrades 43 • Assess change impact • Validate performance before scaling TiDB • Test performance limits For more information, see documentation. 2.2.1.4 SQL • Support

Easy horizontal scaling The TiDB architecture design separates computing from storage, letting you scale out or scale in the computing or storage capacity online as needed. The scaling process is transparent cost-effective solution that adopts a separate comput- ing and storage architecture, enabling easy scaling of computing or storage capacity separately. The computing layer supports a maximum of 512 nodes PD API is called when you retrieve table attributes #55188 @JmPotato • Fix the issue that the scaling progress is displayed incorrectly after the scheduling microservice is enabled #8331 @rleungx •

Easy horizontal scaling The TiDB architecture design separates computing from storage, letting you scale out or scale in the computing or storage capacity online as needed. The scaling process is transparent cost-effective solution that adopts a separate comput- ing and storage architecture, enabling easy scaling of computing or storage capacity separately. The computing layer supports a maximum of 512 nodes manage and maintain connections to TiDB so that they live �→ through rolling restarts, upgrades, or scaling events. �→ Data

Easy horizontal scaling The TiDB architecture design separates computing from storage, letting you scale out or scale in the computing or storage capacity online as needed. The scaling process is transparent cost-effective solution that adopts a separate comput- ing and storage architecture, enabling easy scaling of computing or storage capacity separately. The computing layer supports a maximum of 512 nodes manage and maintain connections to TiDB so that they live �→ through rolling restarts, upgrades, or scaling events. �→ Data

The following video introduces key features of TiDB. 2.1.1 Key features • Horizontally scaling out or scaling in easily The TiDB architecture design of separating computing from storage enables you you to separately scale out or scale in the computing or storage capacity online as needed. The scaling process is transparent to application operations and maintenance staff. • Financial-grade high availability the stress during your application’s peak hours and saves overheads. See Enable TidbCluster Auto-scaling for details. (Introduced in v4.0) 2.4.4 SQL • Use SQL interface to set placement rules for data