如何确认扩容的pd处于正常状态

【 TiDB 使用环境】生产环境 /测试/ Poc
【 TiDB 版本】
【复现路径】做过哪些操作出现的问题
【遇到的问题:问题现象及影响】
【资源配置】
【附件:截图/日志/监控】

目前有3个pd节点,我又同时扩容2个pd节点,现在已经5个pd节点了,我如何确认新的pd已经正常了,我du 新老 pd的data目录大小不一致,历史的399M ,新的才137M

扩容 tidb 节点和 pd 是啥关系。。。。

看 pd 信息可以用 pd-ctl 敲 member

“3个pd节点,我又同时扩容2个tidb 节点,现在已经5个pd节点” :joy:

» member
{
“header”: {
“cluster_id”: 6941116996888182255
},
“members”: [
{
“name”: “pd-10.26.109.62-2379”,
“member_id”: 868986153028076433,
“peer_urls”: [
http://10.26.109.62:2380
],
“client_urls”: [
http://10.26.109.62:2379
],
“deploy_path”: “/export/tidb-deploy/pd-2379/bin”,
“binary_version”: “v4.0.11”,
“git_hash”: “96efd6f402361f2f84e39ea5b3a7a6f6b10acfb1”
},
{
“name”: “pd-10.26.109.61-2379”,
“member_id”: 7277850509584753207,
“peer_urls”: [
http://10.26.109.61:2380
],
“client_urls”: [
http://10.26.109.61:2379
],
“deploy_path”: “/export/tidb-deploy/pd-2379/bin”,
“binary_version”: “v4.0.11”,
“git_hash”: “96efd6f402361f2f84e39ea5b3a7a6f6b10acfb1”
},
{
“name”: “pd-10.26.109.60-2379”,
“member_id”: 11287139224574418821,
“peer_urls”: [
http://10.26.109.60:2380
],
“client_urls”: [
http://10.26.109.60:2379
],
“deploy_path”: “/export/tidb-deploy/pd-2379/bin”,
“binary_version”: “v4.0.11”,
“git_hash”: “96efd6f402361f2f84e39ea5b3a7a6f6b10acfb1”
},
{
“name”: “pd-10.26.109.97-2379”,
“member_id”: 11390822156882166863,
“peer_urls”: [
http://10.26.109.97:2380
],
“client_urls”: [
http://10.26.109.97:2379
],
“deploy_path”: “/export/tidb-deploy/pd-2379/bin”,
“binary_version”: “v4.0.11”,
“git_hash”: “96efd6f402361f2f84e39ea5b3a7a6f6b10acfb1”
},
{
“name”: “pd-10.26.109.98-2379”,
“member_id”: 17258641349127901500,
“peer_urls”: [
http://10.26.109.98:2380
],
“client_urls”: [
http://10.26.109.98:2379
],
“deploy_path”: “/export/tidb-deploy/pd-2379/bin”,
“binary_version”: “v4.0.11”,
“git_hash”: “96efd6f402361f2f84e39ea5b3a7a6f6b10acfb1”
}
],
“leader”: {
“name”: “pd-10.26.109.62-2379”,
“member_id”: 868986153028076433,
“peer_urls”: [
http://10.26.109.62:2380
],
“client_urls”: [
http://10.26.109.62:2379
]
},
“etcd_leader”: {
“name”: “pd-10.26.109.62-2379”,
“member_id”: 868986153028076433,
“peer_urls”: [
http://10.26.109.62:2380
],
“client_urls”: [
http://10.26.109.62:2379
],
“deploy_path”: “/export/tidb-deploy/pd-2379/bin”,
“binary_version”: “v4.0.11”,
“git_hash”: “96efd6f402361f2f84e39ea5b3a7a6f6b10acfb1”
}
}

»

这是相关信息,如何判定已经完全同步了

同时扩容两个PD节点

不好意思,打错了,同时扩容两个PD节点,我已经修改

image

是因为和这个有关吗?

顶一下,希望知道的小伙伴,给出观察指标

member 能看到,进程存活,日志没有 ERROR ,应该就没有问题。
还担心的话 可以用 member transfer 手动将 pd leader 切过去看看正常不正常

1 个赞

扩容成功就属于正常状态了

PD节点的物理文件大小不一样正常吧,tiup display里正常应该就可以。
这又不是tikv的data文件,要保证数据均衡。

1 个赞

感谢各位

此话题已在最后回复的 60 天后被自动关闭。不再允许新回复。