为提高效率,请提供以下信息,问题描述清晰能够更快得到解决:
【TiDB 版本】
TiDB Version: v4.0.3
【问题描述】
PD节点无法启动,启动时报错如下:
pderr.log 每分钟都会出现这个报错:
goroutine 323 [running]:
go.uber.org/zap/zapcore.(*CheckedEntry).Write(0xc0001451e0, 0xc00037ac00, 0x4, 0x4)
/home/jenkins/agent/workspace/build_pd_multi_branch_v4.0.3/go/pkg/mod/go.uber.org/zap@v1.13.0/zapcore/entry.go:230 +0x546
go.uber.org/zap.(*Logger).Panic(0xc000108ea0, 0x23a464a, 0x29, 0xc00037ac00, 0x4, 0x4)
/home/jenkins/agent/workspace/build_pd_multi_branch_v4.0.3/go/pkg/mod/go.uber.org/zap@v1.13.0/logger.go:225 +0x7f
go.etcd.io/etcd/mvcc.(*keyIndex).put(0xc000106c00, 0xc000108ea0, 0x42365ab, 0x0)
/home/jenkins/agent/workspace/build_pd_multi_branch_v4.0.3/go/pkg/mod/go.etcd.io/etcd@v0.5.0-alpha.5.0.20191023171146-3cf2f69b5738/mvcc/key_index.go:82 +0x5fa
go.etcd.io/etcd/mvcc.restoreIntoIndex.func1(0xc0001041c0, 0xc000479a40, 0x2c689e0, 0xc000b25710, 0xc000108ea0)
/home/jenkins/agent/workspace/build_pd_multi_branch_v4.0.3/go/pkg/mod/go.etcd.io/etcd@v0.5.0-alpha.5.0.20191023171146-3cf2f69b5738/mvcc/kvstore.go:505 +0x3e3
created by go.etcd.io/etcd/mvcc.restoreIntoIndex
/home/jenkins/agent/workspace/build_pd_multi_branch_v4.0.3/go/pkg/mod/go.etcd.io/etcd@v0.5.0-alpha.5.0.20191023171146-3cf2f69b5738/mvcc/kvstore.go:473 +0xaa
tiup cluster start cluster_name -N ip:port命令执行时报错
retry error: operation timed out after 2m0s
pd 10.133.1.70:2379 failed to start: timed out waiting for port 2379 to be started after 2m0s, please check the log of the instance
Error: failed to restart: failed to start: failed to start pd: pd 10.133.1.70:2379 failed to start: timed out waiting for port 2379 to be started after 2m0s, please check the log of the instance: timed out waiting for port 2379 to be started after 2m0s
Verbose debug logs has been written to /DATA1/home/tidb/logs/tiup-cluster-debug-2021-05-10-15-23-03.log.
Error: run `` (wd:/DATA1/home/tidb/.tiup/data/SWzTcIG) failed: exit status 1
IP Active: activating (auto-restart) (Result: exit-code) since Mon 2021-05-10 14:49:05 CST; 1s ago
还有一个问题
PD是三副本,一个不能启动,其余正常,但是mydumper备份时,部分表格会报错,原因无法动这个宕机的PD取得相关备份数据。
Error dumping table (SCHEMA.table) data: query metric error: Get http:/IP:port/pd/api/v1/config: dial tcp IP:port: connect: connection refused
感谢请帮忙查看一下
若提问为性能优化、故障排查类问题,请下载脚本运行。终端输出的打印结果,请务必全选并复制粘贴上传。