- Docs Home
- About TiDB Cloud
- Get Started
- Develop Applications
- Overview
- Quick Start
- Build a TiDB Developer Cluster
- CRUD SQL in TiDB
- Build a Simple CRUD App with TiDB
- Example Applications
- Connect to TiDB
- Design Database Schema
- Write Data
- Read Data
- Transaction
- Optimize
- Troubleshoot
- Reference
- Cloud Native Development Environment
- Manage Cluster
- Plan Your Cluster
- Create a TiDB Cluster
- Connect to Your TiDB Cluster
- Set Up VPC Peering Connections
- Use an HTAP Cluster with TiFlash
- Scale a TiDB Cluster
- Upgrade a TiDB Cluster
- Delete a TiDB Cluster
- Use TiDB Cloud API (Beta)
- Migrate Data
- Import Sample Data
- Migrate Data into TiDB
- Configure Amazon S3 Access and GCS Access
- Migrate from MySQL-Compatible Databases
- Migrate Incremental Data from MySQL-Compatible Databases
- Migrate from Amazon Aurora MySQL in Bulk
- Import or Migrate from Amazon S3 or GCS to TiDB Cloud
- Import CSV Files from Amazon S3 or GCS into TiDB Cloud
- Import Apache Parquet Files from Amazon S3 or GCS into TiDB Cloud
- Troubleshoot Access Denied Errors during Data Import from Amazon S3
- Export Data from TiDB
- Back Up and Restore
- Monitor and Alert
- Overview
- Built-in Monitoring
- Built-in Alerting
- Third-Party Monitoring Integrations
- Tune Performance
- Overview
- Analyze Performance
- SQL Tuning
- Overview
- Understanding the Query Execution Plan
- SQL Optimization Process
- Overview
- Logic Optimization
- Physical Optimization
- Prepare Execution Plan Cache
- Control Execution Plans
- TiKV Follower Read
- Coprocessor Cache
- Garbage Collection (GC)
- Tune TiFlash performance
- Manage User Access
- Billing
- Reference
- TiDB Cluster Architecture
- TiDB Cloud Cluster Limits and Quotas
- TiDB Limitations
- SQL
- Explore SQL with TiDB
- SQL Language Structure and Syntax
- SQL Statements
ADD COLUMNADD INDEXADMINADMIN CANCEL DDLADMIN CHECKSUM TABLEADMIN CHECK [TABLE|INDEX]ADMIN SHOW DDL [JOBS|QUERIES]ALTER DATABASEALTER INDEXALTER TABLEALTER TABLE COMPACTALTER USERANALYZE TABLEBATCHBEGINCHANGE COLUMNCOMMITCHANGE DRAINERCHANGE PUMPCREATE [GLOBAL|SESSION] BINDINGCREATE DATABASECREATE INDEXCREATE ROLECREATE SEQUENCECREATE TABLE LIKECREATE TABLECREATE USERCREATE VIEWDEALLOCATEDELETEDESCDESCRIBEDODROP [GLOBAL|SESSION] BINDINGDROP COLUMNDROP DATABASEDROP INDEXDROP ROLEDROP SEQUENCEDROP STATSDROP TABLEDROP USERDROP VIEWEXECUTEEXPLAIN ANALYZEEXPLAINFLASHBACK TABLEFLUSH PRIVILEGESFLUSH STATUSFLUSH TABLESGRANT <privileges>GRANT <role>INSERTKILL [TIDB]MODIFY COLUMNPREPARERECOVER TABLERENAME INDEXRENAME TABLEREPLACEREVOKE <privileges>REVOKE <role>ROLLBACKSELECTSET DEFAULT ROLESET [NAMES|CHARACTER SET]SET PASSWORDSET ROLESET TRANSACTIONSET [GLOBAL|SESSION] <variable>SHOW ANALYZE STATUSSHOW [GLOBAL|SESSION] BINDINGSSHOW BUILTINSSHOW CHARACTER SETSHOW COLLATIONSHOW [FULL] COLUMNS FROMSHOW CREATE SEQUENCESHOW CREATE TABLESHOW CREATE USERSHOW DATABASESSHOW DRAINER STATUSSHOW ENGINESSHOW ERRORSSHOW [FULL] FIELDS FROMSHOW GRANTSSHOW INDEX [FROM|IN]SHOW INDEXES [FROM|IN]SHOW KEYS [FROM|IN]SHOW MASTER STATUSSHOW PLUGINSSHOW PRIVILEGESSHOW [FULL] PROCESSSLISTSHOW PROFILESSHOW PUMP STATUSSHOW SCHEMASSHOW STATS_HEALTHYSHOW STATS_HISTOGRAMSSHOW STATS_METASHOW STATUSSHOW TABLE NEXT_ROW_IDSHOW TABLE REGIONSSHOW TABLE STATUSSHOW [FULL] TABLESSHOW [GLOBAL|SESSION] VARIABLESSHOW WARNINGSSHUTDOWNSPLIT REGIONSTART TRANSACTIONTABLETRACETRUNCATEUPDATEUSEWITH
- Data Types
- Functions and Operators
- Overview
- Type Conversion in Expression Evaluation
- Operators
- Control Flow Functions
- String Functions
- Numeric Functions and Operators
- Date and Time Functions
- Bit Functions and Operators
- Cast Functions and Operators
- Encryption and Compression Functions
- Locking Functions
- Information Functions
- JSON Functions
- Aggregate (GROUP BY) Functions
- Window Functions
- Miscellaneous Functions
- Precision Math
- Set Operations
- List of Expressions for Pushdown
- TiDB Specific Functions
- Clustered Indexes
- Constraints
- Generated Columns
- SQL Mode
- Table Attributes
- Transactions
- Views
- Partitioning
- Temporary Tables
- Cached Tables
- Character Set and Collation
- Read Historical Data
- System Tables
mysql- INFORMATION_SCHEMA
- Overview
ANALYZE_STATUSCLIENT_ERRORS_SUMMARY_BY_HOSTCLIENT_ERRORS_SUMMARY_BY_USERCLIENT_ERRORS_SUMMARY_GLOBALCHARACTER_SETSCLUSTER_INFOCOLLATIONSCOLLATION_CHARACTER_SET_APPLICABILITYCOLUMNSDATA_LOCK_WAITSDDL_JOBSDEADLOCKSENGINESKEY_COLUMN_USAGEPARTITIONSPROCESSLISTREFERENTIAL_CONSTRAINTSSCHEMATASEQUENCESSESSION_VARIABLESSLOW_QUERYSTATISTICSTABLESTABLE_CONSTRAINTSTABLE_STORAGE_STATSTIDB_HOT_REGIONS_HISTORYTIDB_INDEXESTIDB_SERVERS_INFOTIDB_TRXTIFLASH_REPLICATIKV_REGION_PEERSTIKV_REGION_STATUSTIKV_STORE_STATUSUSER_PRIVILEGESVIEWS
- System Variables
- API Reference
- Storage Engines
- Dumpling
- Table Filter
- Troubleshoot Inconsistency Between Data and Indexes
- FAQs
- Release Notes
- Support
- Glossary
Scale Your TiDB Cluster
- Currently, you cannot scale a Developer Tier cluster.
- When a cluster is in the scaling status, you cannot perform any new scaling operations on it.
You can scale a TiDB cluster in the following dimensions:
- Node number of TiDB, TiKV, and TiFlash
- Node storage of TiKV and TiFlash
- Node size (including vCPUs and memory) of TiDB, TiKV, and TiFlash
For information about how to determine the size of your TiDB cluster, see Determine Your TiDB Size.
If the node size of TiDB or TiKV is set as 2 vCPU, 8 GiB (Beta) or 4 vCPU, 16 GiB, note the following restrictions. To bypass these restrictions, you can increase your node size first.
- The node quantity of TiDB can only be set to 1 or 2, and the node quantity of TiKV is fixed to 3.
- 2 vCPU TiDB can only be used with 2 vCPU TiKV, and 2 vCPU TiKV can only be used with 2 vCPU TiDB.
- 4 vCPU TiDB can only be used with 4 vCPU TiKV, and 4 vCPU TiKV can only be used with 4 vCPU TiDB.
- TiFlash is unavailable.
Change node number
You can change the number of TiDB, TiKV, or TiFlash nodes.
Increase node number
To increase the number of TiDB, TiKV, or TiFlash nodes, take the following steps:
In the TiDB Cloud console, navigate to the Clusters page for your project.
Find the area of the cluster that you want to scale, and click ... in the upper-right corner of the area.
TipAlternatively, you can also click the name of the cluster that you want to scale on the Clusters page and click ... in the upper-right corner.
Click Scale in the drop-down menu. The Scale window is displayed.
In the Scale window, increase the number of TiDB, TiKV, or TiFlash nodes.
Click Confirm.
Decrease node number
To decrease the number of TiDB nodes, take the following steps:
In the TiDB Cloud console, navigate to the Clusters page for your project.
Find the area of the cluster that you want to scale, and click ... in the upper-right corner of the area.
TipAlternatively, you can also click the name of the cluster that you want to scale on the Clusters page and click ... in the upper-right corner.
Click Scale in the drop-down menu. The Scale window is displayed.
In the Scale window, decrease the number of TiDB nodes.
Click Confirm.
To decrease the number of TiKV or TiFlash nodes, you need to submit a support ticket. The PingCAP support team will contact you and complete the scaling within the agreed time.
Decreasing TiKV or TiFlash node number can be risky, which might lead to insufficient storage space, excessive CPU usage, or excessive memory usage on remaining nodes.
To submit a support ticket, perform the steps in TiDB Cloud Support. For each node to be scaled, provide the following information in the Description box:
- Cluster name: xxx
- Cloud provider: GCP or AWS
- Node type: TiKV or TiFlash
- Current node number: xxx
- Expected node number: xxx
Change node storage
You can change the node storage of TiKV or TiFlash.
Increase node storage
To increase the node storage of TiKV or TiFlash, take the following steps:
In the TiDB Cloud console, navigate to the Clusters page for your project.
Find the area of the cluster that you want to scale, and click ... in the upper-right corner of the area.
TipAlternatively, you can also click the name of the cluster that you want to scale on the Clusters page and click ... in the upper-right corner.
Click Scale in the drop-down menu. The Scale window is displayed.
In the Scale window, increase the node storage of TiKV or TiFlash.
Click Confirm.
AWS has a cooldown period of node storage changes. If your TiDB cluster is hosted by AWS, after changing the node storage of TiKV or TiFlash, you must wait at least six hours before you can change it again.
Decrease node storage
For a running cluster, AWS and Google Cloud do not allow in-place storage capacity downgrade.
Increase node size
When a cluster is running, you cannot increase its node size. To make such changes, take either of the following methods:
Method 1: Increase the node size through backup and restore
You need to create a latest backup of the cluster, delete the cluster, and then increase the node size when you restore the deleted cluster. Before taking this method, make sure the following impacts are acceptable:
- To avoid any data loss during or after the backup, you need to stop the connection to the cluster through your SQL client before creating the backup.
- After you stop the connection to the cluster, your applications running on this cluster cannot provide service normally until the restoring process is completed.
Method 2: Increase the node size through a support ticket
To submit a support ticket, perform the steps in TiDB Cloud Support. The PingCAP support team will contact you and complete the scaling within the agreed time.
For each node to be scaled, provide the following information in the Description box of the ticket:
- Cluster name: xxx
- Cloud provider: GCP or AWS
- Node type: TiDB, TiKV, or TiFlash
- Current node size: xxx
- Expected node size: xxx