From 7696e6c15eaca4de91f6075bbcd11919f5d8a814 Mon Sep 17 00:00:00 2001
From: TomShawn <1135243111@qq.com>
Date: Sat, 12 Oct 2019 17:29:57 +0800
Subject: [PATCH 1/2] toc: refine the sequence of sql statements
---
dev/TOC.md | 2 +-
v2.1/TOC.md | 2 +-
v3.0/TOC.md | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/dev/TOC.md b/dev/TOC.md
index 9ebde330cd8ab..4fe21a5b7c184 100644
--- a/dev/TOC.md
+++ b/dev/TOC.md
@@ -276,10 +276,10 @@
- [`SHOW [FULL] PROCESSSLIST`](/dev/reference/sql/statements/show-processlist.md)
- [`SHOW SCHEMAS`](/dev/reference/sql/statements/show-schemas.md)
- [`SHOW [FULL] TABLES`](/dev/reference/sql/statements/show-tables.md)
+ - [`SHOW TABLE REGIONS`](/dev/reference/sql/statements/show-table-regions.md)
- [`SHOW TABLE STATUS`](/dev/reference/sql/statements/show-table-status.md)
- [`SHOW [GLOBAL|SESSION] VARIABLES`](/dev/reference/sql/statements/show-variables.md)
- [`SHOW WARNINGS`](/dev/reference/sql/statements/show-warnings.md)
- - [`SHOW TABLE REGIONS`](/dev/reference/sql/statements/show-table-regions.md)
- [`SPLIT REGION`](/dev/reference/sql/statements/split-region.md)
- [`START TRANSACTION`](/dev/reference/sql/statements/start-transaction.md)
- [`TRACE`](/dev/reference/sql/statements/trace.md)
diff --git a/v2.1/TOC.md b/v2.1/TOC.md
index 57e3c38ff7e65..0f8bebff1df84 100644
--- a/v2.1/TOC.md
+++ b/v2.1/TOC.md
@@ -268,10 +268,10 @@
- [`SHOW [FULL] PROCESSSLIST`](/v2.1/reference/sql/statements/show-processlist.md)
- [`SHOW SCHEMAS`](/v2.1/reference/sql/statements/show-schemas.md)
- [`SHOW [FULL] TABLES`](/v2.1/reference/sql/statements/show-tables.md)
+ - [`SHOW TABLE REGIONS`](/v2.1/reference/sql/statements/show-table-regions.md)
- [`SHOW TABLE STATUS`](/v2.1/reference/sql/statements/show-table-status.md)
- [`SHOW [GLOBAL|SESSION] VARIABLES`](/v2.1/reference/sql/statements/show-variables.md)
- [`SHOW WARNINGS`](/v2.1/reference/sql/statements/show-warnings.md)
- - [`SHOW TABLE REGIONS`](/v2.1/reference/sql/statements/show-table-regions.md)
- [`SPLIT REGION`](/v2.1/reference/sql/statements/split-region.md)
- [`START TRANSACTION`](/v2.1/reference/sql/statements/start-transaction.md)
- [`TRACE`](/v2.1/reference/sql/statements/trace.md)
diff --git a/v3.0/TOC.md b/v3.0/TOC.md
index 95d9d1ed89009..6fea8030fd259 100644
--- a/v3.0/TOC.md
+++ b/v3.0/TOC.md
@@ -273,10 +273,10 @@
- [`SHOW [FULL] PROCESSSLIST`](/v3.0/reference/sql/statements/show-processlist.md)
- [`SHOW SCHEMAS`](/v3.0/reference/sql/statements/show-schemas.md)
- [`SHOW [FULL] TABLES`](/v3.0/reference/sql/statements/show-tables.md)
+ - [`SHOW TABLE REGIONS`](/v3.0/reference/sql/statements/show-table-regions.md)
- [`SHOW TABLE STATUS`](/v3.0/reference/sql/statements/show-table-status.md)
- [`SHOW [GLOBAL|SESSION] VARIABLES`](/v3.0/reference/sql/statements/show-variables.md)
- [`SHOW WARNINGS`](/v3.0/reference/sql/statements/show-warnings.md)
- - [`SHOW TABLE REGIONS`](/v3.0/reference/sql/statements/show-table-regions.md)
- [`SPLIT REGION`](/v3.0/reference/sql/statements/split-region.md)
- [`START TRANSACTION`](/v3.0/reference/sql/statements/start-transaction.md)
- [`TRACE`](/v3.0/reference/sql/statements/trace.md)
From 8b6a27a65e4a6bf278bc31be10403270f407fbe7 Mon Sep 17 00:00:00 2001
From: TomShawn <1135243111@qq.com>
Date: Tue, 29 Oct 2019 17:05:26 +0800
Subject: [PATCH 2/2] *: remove transaction kv count limit
---
dev/faq/tidb.md | 1 -
dev/reference/transactions/transaction-model.md | 1 -
dev/tidb-in-kubernetes/reference/configuration/tidb-cluster.md | 3 ---
.../tidb-in-kubernetes/reference/configuration/tidb-cluster.md | 3 ---
4 files changed, 8 deletions(-)
diff --git a/dev/faq/tidb.md b/dev/faq/tidb.md
index b64a93db53f3a..8abf3e27036d0 100644
--- a/dev/faq/tidb.md
+++ b/dev/faq/tidb.md
@@ -915,7 +915,6 @@ As distributed transactions need to conduct two-phase commit and the bottom laye
- A transaction is limited to 5000 SQL statements (by default)
- Each Key-Value entry is no more than 6MB
-- The total number of Key-Value entry is no more than 300,000 rows
- The total size of Key-Value entry is no more than 100MB
There are [similar limits](https://cloud.google.com/spanner/docs/limits) on Google Cloud Spanner.
diff --git a/dev/reference/transactions/transaction-model.md b/dev/reference/transactions/transaction-model.md
index 25021dbdf03e5..682d51a369917 100644
--- a/dev/reference/transactions/transaction-model.md
+++ b/dev/reference/transactions/transaction-model.md
@@ -26,7 +26,6 @@ Due to the distributed, 2-phase commit requirement of TiDB, large transactions t
* A transaction is limited to 5000 SQL statements (by default)
* Each Key-Value entry is no more than 6MB
-* The total number of Key-Value entries is no more than 300,000
* The total size of Key-Value entries is no more than 100MB
### Small transactions
diff --git a/dev/tidb-in-kubernetes/reference/configuration/tidb-cluster.md b/dev/tidb-in-kubernetes/reference/configuration/tidb-cluster.md
index 33d52a4a4b0b4..a619b2bc409aa 100644
--- a/dev/tidb-in-kubernetes/reference/configuration/tidb-cluster.md
+++ b/dev/tidb-in-kubernetes/reference/configuration/tidb-cluster.md
@@ -115,9 +115,6 @@ TiDB Operator uses `Helm` to deploy and manage TiDB clusters. The configuration
| `tidb.txnLocalLatchesCapacity` | The capacity of the transaction memory lock. The number of slots corresponding to Hash is automatically adjusted upward to an exponential multiple of `2`. Each slot occupies 32 Bytes of memory. When the range of writing data is relatively wide (such as importing data), setting this parameter too small a value results in lower performance.
If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:
`[txn-local-latches]`
`capacity = 10240000` | `10240000` |
| `tidb.tokenLimit` | The restrictions on TiDB to execute concurrent sessions
If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:
`token-limit = 1000` | `1000` |
| `tidb.memQuotaQuery` | The memory quota for TiDB queries, which is 32GB by default.
If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:
`mem-quota-query = 34359738368` | `34359738368` |
-| `tidb.txnEntryCountLimit` | The limit on the number of entries in a transaction. If TiKV is used as the storage, the entry represents a key-value pair. **Warning:** Do not set this value too large. Otherwise, it might have a big impact on the TiKV cluster. Set this parameter carefully.
If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:
`[performance]`
`txn-entry-count-limit = 300000` | `300000` |
-| `tidb.txnTotalSizeLimit` | The limit on byte size for each entry in a transaction. If TiKV is used as the storage, the entry represents a key-value pair. **Warning:** Do not set this value too large. Otherwise, it might have a big impact on the TiKV cluster. Set this parameter carefully.
If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:
`[performance]`
`txn-total-size-limit = 104857600` | `104857600` |
-| `tidb.enableBatchDml` | Enables batch submission for DML.
If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:
`enable-batch-dml = false` | `false` |
| `tidb.checkMb4ValueInUtf8` | Controls whether to check the `mb4` characters when the character set is `utf8`.
If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:
`check-mb4-value-in-utf8 = true` | `true` |
| `tidb.treatOldVersionUtf8AsUtf8mb4` | This parameter is used for upgrading compatibility. When it is set to `true`, `utf8` character set in the old table/column is treated as `utf8mb4`.
If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:
`treat-old-version-utf8-as-utf8mb4 = true` | `true` |
| `tidb.lease` | The lease time of TiDB Schema lease. It is highly risky to change this parameter. Therefore, it is not recommended to do so unless you know exactly what might be happening.
If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:
`lease = "45s"` | `45s` |
diff --git a/v3.0/tidb-in-kubernetes/reference/configuration/tidb-cluster.md b/v3.0/tidb-in-kubernetes/reference/configuration/tidb-cluster.md
index 9d3eb882c47fd..12daff59fec9c 100644
--- a/v3.0/tidb-in-kubernetes/reference/configuration/tidb-cluster.md
+++ b/v3.0/tidb-in-kubernetes/reference/configuration/tidb-cluster.md
@@ -115,9 +115,6 @@ TiDB Operator uses `Helm` to deploy and manage TiDB clusters. The configuration
| `tidb.txnLocalLatchesCapacity` | The capacity of the transaction memory lock. The number of slots corresponding to Hash is automatically adjusted upward to an exponential multiple of `2`. Each slot occupies 32 Bytes of memory. When the range of writing data is relatively wide (such as importing data), setting this parameter too small a value results in lower performance.
If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:
`[txn-local-latches]`
`capacity = 10240000` | `10240000` |
| `tidb.tokenLimit` | The restrictions on TiDB to execute concurrent sessions
If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:
`token-limit = 1000` | `1000` |
| `tidb.memQuotaQuery` | The memory quota for TiDB queries, which is 32GB by default.
If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:
`mem-quota-query = 34359738368` | `34359738368` |
-| `tidb.txnEntryCountLimit` | The limit on the number of entries in a transaction. If TiKV is used as the storage, the entry represents a key-value pair. **Warning:** Do not set this value too large. Otherwise, it might have a big impact on the TiKV cluster. Set this parameter carefully.
If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:
`[performance]`
`txn-entry-count-limit = 300000` | `300000` |
-| `tidb.txnTotalSizeLimit` | The limit on byte size for each entry in a transaction. If TiKV is used as the storage, the entry represents a key-value pair. **Warning:** Do not set this value too large. Otherwise, it might have a big impact on the TiKV cluster. Set this parameter carefully.
If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:
`[performance]`
`txn-total-size-limit = 104857600` | `104857600` |
-| `tidb.enableBatchDml` | Enables batch submission for DML.
If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:
`enable-batch-dml = false` | `false` |
| `tidb.checkMb4ValueInUtf8` | Controls whether to check the `mb4` characters when the character set is `utf8`.
If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:
`check-mb4-value-in-utf8 = true` | `true` |
| `tidb.treatOldVersionUtf8AsUtf8mb4` | This parameter is used for upgrading compatibility. When it is set to `true`, `utf8` character set in the old table/column is treated as `utf8mb4`.
If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:
`treat-old-version-utf8-as-utf8mb4 = true` | `true` |
| `tidb.lease` | The lease time of TiDB Schema lease. It is highly risky to change this parameter. Therefore, it is not recommended to do so unless you know exactly what might be happening.
If the version of TiDB Operator is later than v1.0.0, configure this parameter via `tidb.config`:
`lease = "45s"` | `45s` |