| title | summary | category | aliases | |
|---|---|---|---|---|
TiDB Cloud Glossary |
Learn the terms used in TiDB Cloud. |
glossary |
|
ACID refers to the four key properties of a transaction: atomicity, consistency, isolation, and durability. Each of these properties is described below.
-
Atomicity means that either all the changes of an operation are performed, or none of them are. TiDB ensures the atomicity of the TiDB Region that stores the Primary Key to achieve the atomicity of transactions.
-
Consistency means that transactions always bring the database from one consistent state to another. In TiDB, data consistency is ensured before writing data to the memory.
-
Isolation means that a transaction in process is invisible to other transactions until it completes. This allows concurrent transactions to read and write data without sacrificing consistency. TiDB currently supports the isolation level of
REPEATABLE READ. -
Durability means that once a transaction is committed, it remains committed even in the event of a system failure. TiKV uses persistent storage to ensure durability.
Determines the functionality and capacity of your cluster. Different cluster tiers provide different numbers of TiDB, TiKV, and TiFlash nodes in your cluster.
TiDB Cloud offers a certain number of credits for Proof of Concept (PoC) users. One credit is equivalent to one U.S. dollar. You can use credits to pay TiDB cluster fees before the credits become expired.
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.
Organization members are users who are invited by the organization owner to join an organization. Organization members can view members of the organization and can be invited to projects within the organization.
Playground contains a pre-loaded dataset of GitHub events, which allows Serverless Tier users to get started with TiDB Cloud by running queries instantly, without importing data or connecting to a client.
You can access Playground after creating a Serverless Tier cluster.
A document that defines permissions applying to a role, user, or organization, such as the access to specific actions or resources.
Based on the projects created by the organization, resources such as personnel, instances, and networks can be managed separately according to projects, and resources between projects do not interfere with each other.
Project members are users who are invited to join one or more projects of the organization. Project members can manage clusters, network access, backups, and other resources.
The place where the data of deleted clusters with valid backups is stored. Once a backed-up cluster is deleted, the existing backup files of the cluster are moved to the recycle bin. For backup files from automatic backups, the recycle bin will retain them for 7 days. For backup files from manual backups, there is no expiration date. To avoid data loss, remember to restore the data to a new cluster in time. Note that if a cluster has no backup, the deleted cluster will not be displayed here.
-
TiDB Cloud region
A geographical area in which a TiDB Cloud cluster is deployed. A TiDB Cloud region comprises of at least 3 Availability Zones, and the cluster is deployed across these zones.
-
TiDB 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 replication of changefeed is charged according to the computing resources, which is the TiCDC replication capacity unit.
The collection of TiDB, TiKV, the Placement Driver (PD), and TiFlash nodes that form a functional working database.
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.
Enables you to connect Virtual Private Cloud (VPC) networks so that workloads in different VPC networks can communicate privately.
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.