Note:
Original topic: tikv aborts txn: Value with size 5080652 exceeded ValueLogFileSize (4194304).
dm cluster version v6.1.0
Error reported during the loader phase in dm:
【TiDB Usage Environment】Production\Test Environment\POCWhat operations were performed to encounter the problem
Relevant logs, configuration files, Grafana monitoring (https://metricstool.pingcap.com/ )
TiUP Cluster Display information
TiUP Cluster Edit config information
TiDB-Overview monitoring
Corresponding module’s Grafana monitoring (if any, such as BR, TiDB-binlog, TiCDC, etc.)
Corresponding module logs (including logs from 1 hour before and after the issue)
If the question is related to performance optimization or fault troubleshooting , please download the script and run it. Please select all and copy-paste the terminal output results for upload.
Known bug: the configuration parameter for Entity Size is not supported in TiDB.
opened 04:59AM - 04 Jul 22 UTC
closed 09:51AM - 08 Jul 22 UTC
type/bug
severity/major
area/dm
affects-6.0
affects-6.1
### What did you do?
https://asktug.com/t/topic/694876
TiDB config:
```
+-… -----+---------------------+--------------------------------------+-----------+
| Type | Instance | Name | Value |
+------+---------------------+--------------------------------------+-----------+
| tidb | xxxxx:4000 | performance.txn-entry-size-limit | 125829120 |
| tikv | xxxxx:20161 | raftstore.raft-entry-max-size | 128MiB |
+------+---------------------+--------------------------------------+-----------+
```
DM error:
```
"errors": [
{
"ErrCode": 50000,
"ErrClass": "not-set",
"ErrScope": "not-set",
"ErrLevel": "high",
"Message": "[kv:8025]entry too large, the max entry size is 6291456, the size of data is 7890542",
"RawCause": "",
"Workaround": ""
}
],
```
### What did you expect to see?
DM task work normally.
### What did you see instead?
DM task get an error.
### Versions of the cluster
DM version (run `dmctl -V` or `dm-worker -V` or `dm-master -V`):
```
tiup is checking updates for component dmctl ...
Starting component `dmctl`: /home/admin/.tiup/components/dmctl/v6.1.0/dmctl/dmctl -V
Release Version: v6.1.0
Git Commit Hash: 9f5e3cea2fae0a3dce6cc5ca79e3bcd654b8aa99
Git Branch: heads/refs/tags/v6.1.0
UTC Build Time: 2022-06-07 11:55:24
Go Version: go version go1.18.2 linux/amd64
```
TiDB Version
```
MySQL [(none)]> SELECT tidb_version()\G
*************************** 1. row ***************************
tidb_version(): Release Version: v6.1.0
Edition: Community
Git Commit Hash: https://github.com/pingcap/tidb/commit/1a89decdb192cbdce6a7b0020d71128bc964d30f
Git Branch: heads/refs/tags/v6.1.0
UTC Build Time: 2022-06-05 05:15:11
GoVersion: go1.18.2
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false
1 row in set (0.00 sec)
```
### current status of DM cluster (execute `query-status <task-name>` in dmctl)
```console
(paste current status of DM cluster here)
```
The suggestion is to split the task, referring to the post below:
Custom configuration has been done.
How to configure it? What to configure? Please provide guidance.
His error is different from mine. My error is:
I couldn’t find the parameter with a default value of 4194304 on the official website.
It’s already a known BUG…
I am currently merging 800 MySQL sharded tables into 9 tables in TiDB. I will try to split the task.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: Johnpan
|
username: 
|
username: 
|
username: