- Quick Start
- Use Your Cluster
- Connect to Your TiDB Cluster
- Set Up VPC Peering Connections
- Monitor a TiDB Cluster
- Scale a TiDB Cluster
- Use an HTAP Cluster
- Backup and Restore Data
- Tune Performance
- Upgrade a TiDB Cluster
- Delete a TiDB Cluster
- Migrate Data
- Manage User Access
Determines the functionality and capacity of your cluster. Different cluster tiers provide different numbers of TiDB, TiKV, and TiFlash nodes in your cluster.
A user that has been invited to an organization, with access to the organization and the clusters of this organization.
Refers to either a data instance (TiKV) or a compute instance (TiDB) or an analytical instance (TiFlash).
An entity that you create to manage your TiDB Cloud accounts, including a management account with any number of multiple member accounts.
A document that defines permissions applying to a role, user, or organization, such as the access to specific actions or resources.
The place where the data of deleted clusters with valid backups is stored. The deleted data or backup files will be retained here for a certain duration of time based on your plan. To avoid data loss, remember to restore the data to a new cluster in time. Note that if a cluster has no backup file, the deleted cluster will not appear here.
TiDB Cloud region
A set of TiKV nodes deployed in the same geographical area. The set of TiKV nodes will be deployed across at least three different Availability Zones within that region.
The basic unit of data in TiDB. TiKV divides the Key-Value space into a series of consecutive Key segments, and each segment is called a Region. The default size limit for each Region is 96 MB and can be configured.
A separate database that can be located in the same or different region and contains the same data. A replica is often used for disaster recovery purposes or to improve performance.
The computing node that aggregates data from queries returned from transactional or analytical stores. Increasing the number of TiDB nodes will increase the number of concurrent queries that the cluster can handle.
The analytical storage node that replicates data from TiKV in real time and supports real-time analytical workloads.
The storage node that stores the online transactional processing (OLTP) data. It is scaled in multiples of 3 nodes (for example, 3, 6, 9) for high availability, with two nodes acting as replicas. Increasing the number of TiKV nodes will increase the total throughput.
A list of IP addresses and Classless Inter-Domain Routing (CIDR) addresses that are allowed to access the TiDB Cloud cluster via a SQL client. The traffic filter is empty by default.
A logically isolated virtual network partition that provides managed networking service for your resources.
Short for Virtual Private Cloud.
A networking connection between two Virtual Private Clouds (VPCs) that enables you to route traffic between them using private IP addresses and helps you to facilitate data transfer.