-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dm6.5,资源耗尽 #10429
Comments
can you provide the task configuration? |
配置肯定没问题啊,配置要是有问题,检查不能报这个错 |
这个项目还有人在维护么? |
// 增加调用选项 grpc.WithDefaultCallOptions(grpc.MaxCallRecvMsgSize(recvSize))) // 其实也一样, 设置一下发送 接收的大小
|
we will fix it in v8.0 and pick to v6.5.8 |
/severity moderate |
What did you do?
mysql同步到tidb,源实例400+schema,2.5w+tables
What did you expect to see?
No response
What did you see instead?
启动task报错
ERROR] [subtask.go:218] ["fail to initialize subtask"] [subtask=aaa] [error="[code=42501:class=ha:scope=internal:level=high], Message: fail to initialize unit Sync of subtask aaa: fail to do etcd txn operation: txn commit failed, RawCause: rpc error: code = ResourceExhausted desc = trying to send message larger than max (2157479 vs. 2097152), Workaround: Please check dm-master's node status and the network between this node and dm-master"]
Versions of the cluster
Release Version: v6.5.0
Git Commit Hash: 9e91cff
Git Branch: heads/refs/tags/v6.5.0
UTC Build Time: 2022-12-23 08:44:26
Go Version: go version go1.19.3 linux/amd64
Failpoint Build: false
Release Version: v6.5.0
Git Commit Hash: 9e91cff
Git Branch: heads/refs/tags/v6.5.0
UTC Build Time: 2022-12-23 08:44:26
Go Version: go version go1.19.3 linux/amd64
Failpoint Build: false
current status of DM cluster (execute
query-status <task-name>
in dmctl)"stage": "Paused",
"unit": "InvalidUnit",
"result": {
"isCanceled": false,
"errors": [
{
"ErrCode": 42501,
"ErrClass": "ha",
"ErrScope": "internal",
"ErrLevel": "high",
"Message": "fail to initialize unit Sync of subtask aaa: fail to do etcd txn operation: txn commit failed",
"RawCause": "rpc error: code = ResourceExhausted desc = trying to send message larger than max (2157479 vs. 2097152)",
"Workaround": "Please check dm-master's node status and the network between this node and dm-master"
}
],
"detail": null
The text was updated successfully, but these errors were encountered: