Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: pd缩容后日志报错无法连接到下线的pd节点
|
username: TiDBer_yUoxD0vR
[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Problem Phenomenon and Impact]
The PD node (192.168.133.113:2379) went offline, but the logs of other PD nodes kept reporting errors that they couldn’t connect to this node. The error only disappeared after restarting the PD nodes. Can’t PD detect that a PD node has gone offline? Using pt-ctl shows no offline nodes.
[WARN] [grpclog.go:60] [“grpc: addrConn.createTransport failed to connect to {192.168.133.113:2379 0 }. Err: connection error: desc = "transport: Error while dialing dial tcp 192.168.133.113:2379: connect: connection refused". Reconnecting…”]
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots/Logs/Monitoring]
|
username: 
|
username: 
|
username: 
|
username: 
|
username: