You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -28,7 +30,7 @@ ACID refers to the four key properties of a transaction: atomicity, consistency,
28
30
29
31
-**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.
30
32
31
-
## B
33
+
## <aid="B"class="letter"href="#B">B</a>
32
34
33
35
### Backup & Restore (BR)
34
36
@@ -48,7 +50,7 @@ The Batch Create Table feature greatly speeds up the creation of multiple tables
48
50
49
51
A [Region](#regionpeerraft-group) is logically divided into several small ranges called bucket. TiKV collects query statistics by buckets and reports the bucket status to PD. For more information, see the [Bucket design doc](https://github.com/tikv/rfcs/blob/master/text/0082-dynamic-size-region.md#bucket).
50
52
51
-
## C
53
+
## <aid="C"class="letter"href="#C">C</a>
52
54
53
55
### Cached Table
54
56
@@ -86,7 +88,7 @@ Continuous Profiling is a way to observe resource overhead at the system call le
86
88
87
89
Coprocessor is a coprocessing mechanism that shares the computation workload with TiDB. It is located in the storage layer (TiKV or TiFlash) and collaboratively processes computations [pushed down](/functions-and-operators/expressions-pushed-down.md) from TiDB on a per-Region basis.
88
90
89
-
## D
91
+
## <aid="D"class="letter"href="#D">D</a>
90
92
91
93
### Dumpling
92
94
@@ -122,15 +124,15 @@ Distributed eXecution Framework (DXF) is the framework used by TiDB to centrally
122
124
123
125
Dynamic pruning mode is one of the modes that TiDB accesses partitioned tables. In dynamic pruning mode, each operator supports direct access to multiple partitions. Therefore, TiDB no longer uses Union. Omitting the Union operation can improve the execution efficiency and avoid the problem of Union concurrent execution.
124
126
125
-
## E
127
+
## <aid="E"class="letter"href="#E">E</a>
126
128
127
129
### Expression index
128
130
129
131
The expression index is a special type of index created on an expression. Once an expression index is created, TiDB can use this index for expression-based queries, significantly improving query performance.
130
132
131
133
For more information, see [CREATE INDEX - Expression index](/sql-statements/sql-statement-create-index.md#expression-index).
132
134
133
-
## G
135
+
## <aid="G"class="letter"href="#G">G</a>
134
136
135
137
### Garbage Collection (GC)
136
138
@@ -144,7 +146,7 @@ General Availability (GA) of a feature means the feature is fully tested and is
144
146
145
147
Global Transaction Identifiers (GTIDs) are unique transaction IDs used in MySQL binary logs to track which transactions have been replicated. [Data Migration (DM)](/dm/dm-overview.md) uses these IDs to ensure consistent replication.
146
148
147
-
## H
149
+
## <aid="H"class="letter"href="#H">H</a>
148
150
149
151
### Hotspot
150
152
@@ -154,7 +156,7 @@ Hotspot refers to a situation where the read and write workloads in TiKV are con
154
156
155
157
Hybrid Transactional and Analytical Processing (HTAP) is a database feature that enables both OLTP (Online Transactional Processing) and OLAP (Online Analytical Processing) workloads within the same database. For TiDB, the HTAP feature is provided by using TiKV for row storage and TiFlash for columnar storage. For more information, see [Quick Start with TiDB HTAP](/quick-start-with-htap.md) and [Explore HTAP](/explore-htap.md).
156
158
157
-
## I
159
+
## <aid="I"class="letter"href="#I">I</a>
158
160
159
161
### In-Memory Pessimistic Lock
160
162
@@ -164,7 +166,7 @@ The in-memory pessimistic lock is a new feature introduced in TiDB v6.0.0. When
164
166
165
167
Index Merge is a method introduced in TiDB v4.0 to access tables. Using this method, the TiDB optimizer can use multiple indexes per table and merge the results returned by each index. In some scenarios, this method makes the query more efficient by avoiding full table scans. Since v5.4, Index Merge has become a GA feature.
166
168
167
-
## K
169
+
## <aid="K"class="letter"href="#K">K</a>
168
170
169
171
### Key Management Service (KMS)
170
172
@@ -174,7 +176,7 @@ Key Management Service (KMS) enables the storage and retrieval of secret keys in
174
176
175
177
Key-Value (KV) is a way of storing information by associating values with unique keys, allowing quick data retrieval. TiDB uses TiKV to map tables and indexes into key-value pairs, enabling efficient data storage and access across the database.
176
178
177
-
## L
179
+
## <aid="L"class="letter"href="#L">L</a>
178
180
179
181
### Leader/Follower/Learner
180
182
@@ -194,7 +196,7 @@ For more information, see system table documentation: [`TIDB_TRX`](/information-
194
196
195
197
Long Term Support (LTS) refers to software versions that are extensively tested and maintained for extended periods. For more information, see [TiDB Versioning](/releases/versioning.md).
[MVCC](https://en.wikipedia.org/wiki/Multiversion_concurrency_control) is a concurrency control mechanism in TiDB and other databases. It processes the memory read by transactions to achieve concurrent access to TiDB, thereby avoiding blocking caused by conflicts between concurrent reads and writes.
206
208
207
-
## O
209
+
## <aid="O"class="letter"href="#O">O</a>
208
210
209
211
### Old value
210
212
@@ -247,7 +249,7 @@ Optimistic transactions are transactions that use optimistic concurrency control
247
249
248
250
For more information, see [TiDB Optimistic Transaction Model](/optimistic-transaction.md).
249
251
250
-
## P
252
+
## <aid="P"class="letter"href="#P">P</a>
251
253
252
254
### Partitioning
253
255
@@ -283,7 +285,7 @@ Point in Time Recovery (PITR) enables you to restore data to a specific point in
283
285
284
286
In most cases, when executing SQL statements, the optimizer only uses statistics of some columns (such as columns in the `WHERE`, `JOIN`, `ORDER BY`, and `GROUP BY` statements). These used columns are called predicate columns. For more information, see [Collect statistics on some columns](/statistics.md#collect-statistics-on-some-columns).
285
287
286
-
## Q
288
+
## <aid="Q"class="letter"href="#Q">Q</a>
287
289
288
290
### Queries Per Second (QPS)
289
291
@@ -293,7 +295,7 @@ Queries Per Second (QPS) is the number of queries a database service handles per
293
295
294
296
Quota Limiter is an experimental feature introduced in TiDB v6.0.0. If the machine on which TiKV is deployed has limited resources, for example, with only 4v CPU and 16 G memory, and the foreground of TiKV processes too many read and write requests, the CPU resources used by the background are occupied to help process such requests, which affects the performance stability of TiKV. To avoid this situation, the [quota-related configuration items](/tikv-configuration-file.md#quota) can be set to limit the CPU resources to be used by the foreground.
295
297
296
-
## R
298
+
## <aid="R"class="letter"href="#R">R</a>
297
299
298
300
### Raft Engine
299
301
@@ -325,7 +327,7 @@ Restore is the reverse of the backup operation. It is the process of bringing ba
325
327
326
328
[RocksDB](https://rocksdb.org/) is an LSM-tree structured engine that provides key-value storage and read-write functionality. It was developed by Facebook and is based on LevelDB. RocksDB is the core storage engine of TiKV.
327
329
328
-
## S
330
+
## <aid="S"class="letter"href="#S">S</a>
329
331
330
332
### Scheduler
331
333
@@ -356,7 +358,7 @@ Static Sorted Table or Sorted String Table is a file storage format used in Rock
356
358
357
359
A store refers to the storage node in the TiKV cluster (an instance of `tikv-server`). Each store has a corresponding TiKV instance.
358
360
359
-
## T
361
+
## <aid="T"class="letter"href="#T">T</a>
360
362
361
363
### Temporary table
362
364
@@ -398,7 +400,7 @@ Top SQL helps locate SQL queries that contribute to a high load of a TiDB or TiK
398
400
399
401
Transactions Per Second (TPS) is the number of transactions a database processes per second, serving as a key metric for measuring database performance and throughput.
400
402
401
-
## U
403
+
## <aid="U"class="letter"href="#U">U</a>
402
404
403
405
### Uniform Resource Identifier (URI)
404
406
@@ -408,7 +410,7 @@ Uniform Resource Identifier (URI) is a standardized format for identifying a res
408
410
409
411
Universally Unique Identifier (UUID) is a 128-bit (16-byte) generated ID used to uniquely identify records in a database. For more information, see [UUID](/best-practices/uuid.md).
0 commit comments