【 TiDB 使用环境】测试
【 TiDB 版本】V7.4.0
【复现路径】tiup dm start dm-test 初次启动时出现
【遇到的问题：问题现象及影响】worker 节点 fail to dial dm-master，DM 集群启动报错
【资源配置】2核8G
【附件：截图/日志/监控】
日志1：
[2023/10/16 11:53:08.137 +08:00] [ERROR] [join.go:65] [“fail to dial dm-master”] [endpoint=http://43.138.205.213:8261] [error=“context deadline exceeded”]
[2023/10/16 11:53:08.137 +08:00] [INFO] [main.go:71] [“join the cluster meet error”] [error=“[code=40077:class=dm-worker:scope=internal:level=high], Message: cannot join with master endpoints: [http://43.138.205.213:8261], error: context deadline exceeded, Workaround: Please check network connection of worker and check worker name is unique.”] [errorVerbose=“[code=40077:class=dm-worker:scope=internal:level=high], Message: cannot join with master endpoints: [http://43.138.205.213:8261], error: context deadline exceeded, Workaround: Please check network connection of worker and check worker name is unique.\ngithub.com/pingcap/tiflow/dm/pkg/terror.(*Error).Generate\n\tgithub.com/pingcap/tiflow/dm/pkg/terror/terror.go:293\ngithub.com/pingcap/tiflow/dm/worker.(*Server).JoinMaster\n\tgithub.com/pingcap/tiflow/dm/worker/join.go:86\nmain.main\n\tgithub.com/pingcap/tiflow/cmd/dm-worker/main.go:69\nruntime.main\n\truntime/proc.go:267\nruntime.goexit\n\truntime/asm_amd64.s:1650”]
日志2：
| 2023-10-16T11:46:17.738+0800 | DEBUG | retry error | {error: operation timed out after 2m0s} |
|---|---|---|---|
| 2023-10-16T11:46:17.738+0800 | DEBUG | TaskFinish | {task: StartCluster, error: failed to start dm-worker: failed to start: 43.138.205.213 dm-worker-8265.service, please check the instance’s log(/home/tidb/dm/deploy/dm-worker-8265/log) for more detail.: timed out waiting for port 8265 to be started after 2m0s, errorVerbose: timed out waiting for port 8265 to be started after 2m0s\ngithub.com/pingcap/tiup/pkg/cluster/module.(*WaitFor).Execute\n\tgithub.com/pingcap/tiup/pkg/cluster/module/wait_for.go:91\ngithub.com/pingcap/tiup/pkg/cluster/spec.PortStarted\n\tgithub.com/pingcap/tiup/pkg/cluster/spec/instance.go:123\ngithub.com/pingcap/tiup/pkg/cluster/spec.(*BaseInstance).Ready\n\tgithub.com/pingcap/tiup/pkg/cluster/spec/instance.go:157\ngithub.com/pingcap/tiup/pkg/cluster/operation.startInstance\n\tgithub.com/pingcap/tiup/pkg/cluster/operation/action.go:405\ngithub.com/pingcap/tiup/pkg/cluster/operation.StartComponent.func1\n\tgithub.com/pingcap/tiup/pkg/cluster/operation/action.go:534\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.1.0/errgroup/errgroup.go:75\nruntime.goexit\n\truntime/asm_amd64.s:1650\nfailed to start: 43.138.205.213 dm-worker-8265.service, please check the instance’s log(/home/tidb/dm/deploy/dm-worker-8265/log) for more detail.\nfailed to start dm-worker} |
| 2023-10-16T11:46:17.738+0800 | INFO | Execute command finished | {code: 1, error: failed to start dm-worker: failed to start: 43.138.205.213 dm-worker-8265.service, please check the instance’s log(/home/tidb/dm/deploy/dm-worker-8265/log) for more detail.: timed out waiting for port 8265 to be started after 2m0s, errorVerbose: timed out waiting for port 8265 to be started after 2m0s\ngithub.com/pingcap/tiup/pkg/cluster/module.(*WaitFor).Execute\n\tgithub.com/pingcap/tiup/pkg/cluster/module/wait_for.go:91\ngithub.com/pingcap/tiup/pkg/cluster/spec.PortStarted\n\tgithub.com/pingcap/tiup/pkg/cluster/spec/instance.go:123\ngithub.com/pingcap/tiup/pkg/cluster/spec.(*BaseInstance).Ready\n\tgithub.com/pingcap/tiup/pkg/cluster/spec/instance.go:157\ngithub.com/pingcap/tiup/pkg/cluster/operation.startInstance\n\tgithub.com/pingcap/tiup/pkg/cluster/operation/action.go:405\ngithub.com/pingcap/tiup/pkg/cluster/operation.StartComponent.func1\n\tgithub.com/pingcap/tiup/pkg/cluster/operation/action.go:534\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.1.0/errgroup/errgroup.go:75\nruntime.goexit\n\truntime/asm_amd64.s:1650\nfailed to start: 43.138.205.213 dm-worker-8265.service, please check the instance’s log(/home/tidb/dm/deploy/dm-worker-8265/log) for more detail.\nfailed to start dm-worker} |
DM配置：
