From 0e5462f54590fe5702676fefcc1a1465c4202ac4 Mon Sep 17 00:00:00 2001 From: doc-claw-bot Date: Wed, 22 Jul 2026 15:47:35 +0000 Subject: [PATCH 1/4] docs: clarify TiKV limit for large rows --- develop/dev-guide-transaction-restraints.md | 1 + 1 file changed, 1 insertion(+) diff --git a/develop/dev-guide-transaction-restraints.md b/develop/dev-guide-transaction-restraints.md index 315a2841b92c2..185f0e52b6a2b 100644 --- a/develop/dev-guide-transaction-restraints.md +++ b/develop/dev-guide-transaction-restraints.md @@ -713,6 +713,7 @@ The basic principle is to limit the size of the transaction. At the KV level, Ti - You can adjust it by using the [`performance.txn-entry-size-limit`](https://docs.pingcap.com/tidb/stable/tidb-configuration-file#txn-entry-size-limit-new-in-v4010-and-v500) configuration parameter of tidb-server for TiDB v4.0.10 and later v4.0.x versions, TiDB v5.0.0 and later versions. The value is `6 MB` for versions earlier than v4.0.10. - Starting from v7.6.0, you can use the [`tidb_txn_entry_size_limit`](/system-variables.md#tidb_txn_entry_size_limit-new-in-v760) system variable to dynamically modify the value of this configuration item. + - Note that TiKV has a similar limit. If the data size of a single write request exceeds [`raftstore.raft-entry-max-size`](/tikv-configuration-file.md#raft-entry-max-size), which is `8 MiB` by default, TiKV rejects the request. When a table contains a large row, you need to adjust both limits at the same time. - The maximum single transaction size supported is 1 TiB. From d4eb149b5eb7c6e87dd7cb40637fcaf3781aadb4 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Thu, 23 Jul 2026 16:29:31 +0800 Subject: [PATCH 2/4] Update develop/dev-guide-transaction-restraints.md --- develop/dev-guide-transaction-restraints.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/develop/dev-guide-transaction-restraints.md b/develop/dev-guide-transaction-restraints.md index 185f0e52b6a2b..361c141b421b2 100644 --- a/develop/dev-guide-transaction-restraints.md +++ b/develop/dev-guide-transaction-restraints.md @@ -713,7 +713,7 @@ The basic principle is to limit the size of the transaction. At the KV level, Ti - You can adjust it by using the [`performance.txn-entry-size-limit`](https://docs.pingcap.com/tidb/stable/tidb-configuration-file#txn-entry-size-limit-new-in-v4010-and-v500) configuration parameter of tidb-server for TiDB v4.0.10 and later v4.0.x versions, TiDB v5.0.0 and later versions. The value is `6 MB` for versions earlier than v4.0.10. - Starting from v7.6.0, you can use the [`tidb_txn_entry_size_limit`](/system-variables.md#tidb_txn_entry_size_limit-new-in-v760) system variable to dynamically modify the value of this configuration item. - - Note that TiKV has a similar limit. If the data size of a single write request exceeds [`raftstore.raft-entry-max-size`](/tikv-configuration-file.md#raft-entry-max-size), which is `8 MiB` by default, TiKV rejects the request. When a table contains a large row, you need to adjust both limits at the same time. + - Note that TiKV also has a limit on the data size of a single write request. If the data size of a single write request exceeds [`raftstore.raft-entry-max-size`](/tikv-configuration-file.md#raft-entry-max-size), which is `8 MiB` by default, TiKV rejects the request. When a single row is large, you need to adjust both `tidb_txn_entry_size_limit` in TiDB and `raftstore.raft-entry-max-size` in TiKV. - The maximum single transaction size supported is 1 TiB. From ed0a3880463a2bdda2b3059c0adbed7b35336a15 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Thu, 23 Jul 2026 16:30:33 +0800 Subject: [PATCH 3/4] Update develop/dev-guide-transaction-restraints.md --- develop/dev-guide-transaction-restraints.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/develop/dev-guide-transaction-restraints.md b/develop/dev-guide-transaction-restraints.md index 361c141b421b2..722a73bf2b91d 100644 --- a/develop/dev-guide-transaction-restraints.md +++ b/develop/dev-guide-transaction-restraints.md @@ -713,7 +713,7 @@ The basic principle is to limit the size of the transaction. At the KV level, Ti - You can adjust it by using the [`performance.txn-entry-size-limit`](https://docs.pingcap.com/tidb/stable/tidb-configuration-file#txn-entry-size-limit-new-in-v4010-and-v500) configuration parameter of tidb-server for TiDB v4.0.10 and later v4.0.x versions, TiDB v5.0.0 and later versions. The value is `6 MB` for versions earlier than v4.0.10. - Starting from v7.6.0, you can use the [`tidb_txn_entry_size_limit`](/system-variables.md#tidb_txn_entry_size_limit-new-in-v760) system variable to dynamically modify the value of this configuration item. - - Note that TiKV also has a limit on the data size of a single write request. If the data size of a single write request exceeds [`raftstore.raft-entry-max-size`](/tikv-configuration-file.md#raft-entry-max-size), which is `8 MiB` by default, TiKV rejects the request. When a single row is large, you need to adjust both `tidb_txn_entry_size_limit` in TiDB and `raftstore.raft-entry-max-size` in TiKV. + - Note that TiKV also limits the data size of a single write request. If the data size of a single write request exceeds [`raftstore.raft-entry-max-size`](/tikv-configuration-file.md#raft-entry-max-size), which is `8 MiB` by default, TiKV rejects the request. When a single row is large, you need to adjust both `tidb_txn_entry_size_limit` in TiDB and `raftstore.raft-entry-max-size` in TiKV. - The maximum single transaction size supported is 1 TiB. From 6adacb96f98a5a97ac46cb194b15ba41c113e728 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Thu, 23 Jul 2026 16:52:33 +0800 Subject: [PATCH 4/4] Update develop/dev-guide-transaction-restraints.md --- develop/dev-guide-transaction-restraints.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/develop/dev-guide-transaction-restraints.md b/develop/dev-guide-transaction-restraints.md index 722a73bf2b91d..d27f6cfc4ab59 100644 --- a/develop/dev-guide-transaction-restraints.md +++ b/develop/dev-guide-transaction-restraints.md @@ -713,7 +713,7 @@ The basic principle is to limit the size of the transaction. At the KV level, Ti - You can adjust it by using the [`performance.txn-entry-size-limit`](https://docs.pingcap.com/tidb/stable/tidb-configuration-file#txn-entry-size-limit-new-in-v4010-and-v500) configuration parameter of tidb-server for TiDB v4.0.10 and later v4.0.x versions, TiDB v5.0.0 and later versions. The value is `6 MB` for versions earlier than v4.0.10. - Starting from v7.6.0, you can use the [`tidb_txn_entry_size_limit`](/system-variables.md#tidb_txn_entry_size_limit-new-in-v760) system variable to dynamically modify the value of this configuration item. - - Note that TiKV also limits the data size of a single write request. If the data size of a single write request exceeds [`raftstore.raft-entry-max-size`](/tikv-configuration-file.md#raft-entry-max-size), which is `8 MiB` by default, TiKV rejects the request. When a single row is large, you need to adjust both `tidb_txn_entry_size_limit` in TiDB and `raftstore.raft-entry-max-size` in TiKV. + - Note that TiKV also limits the data size of a single write request. If the data size of a single write request exceeds [`raftstore.raft-entry-max-size`](/tikv-configuration-file.md#raft-entry-max-size), which is `8 MiB` by default, TiKV rejects the request. When a single row is large, you need to adjust both `tidb_txn_entry_size_limit` for TiDB and `raftstore.raft-entry-max-size` for TiKV. - The maximum single transaction size supported is 1 TiB.