PD Log Error ["transport: Got too many pings from the client, closing the connection."]

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: PD 日志报错[“transport: Got too many pings from the client, closing the connection.”]

| username: xingzhenxiang

[TiDB Usage Environment] Production Environment / Testing / Poc
[TiDB Version] 6.5.1
[Reproduction Path] Operations performed that led to the issue
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration]
[Attachments: Screenshots / Logs / Monitoring]

[2023/03/31 02:02:37.240 +08:00] [ERROR] [grpclog.go:75] [“transport: Got too many pings from the client, closing the connection.”]
[2023/03/31 02:02:37.240 +08:00] [ERROR] [grpclog.go:75] [“transport: loopyWriter.run returning. Err: transport: Connection closing”]
[2023/03/31 02:03:15.913 +08:00] [ERROR] [grpclog.go:75] [“transport: Got too many pings from the client, closing the connection.”]
[2023/03/31 02:03:15.913 +08:00] [ERROR] [grpclog.go:75] [“transport: loopyWriter.run returning. Err: transport: Connection closing”]

| username: CuteRay | Original post link

I encountered the same issue with the 6.5.1 community version. As soon as it’s deployed, without doing anything, it reports an error after a few minutes.

| username: xingzhenxiang | Original post link

Are you also panicking? Please ask the official team to take a look.

| username: GreenGuan | Original post link

In my environment, which is also 651, I haven’t encountered this error. May I ask what impact this error has on the TiDB cluster?

| username: TiDBer_pkQ5q1l0 | Original post link

I have it here too, I guess it’s a BUG. Not sure if it exists in version 6.5.0.

| username: xingzhenxiang | Original post link

I found that my PD leader switched. I am investigating it and currently tracking the issue.

| username: xingzhenxiang | Original post link

Let’s wait for the official confirmation to see if there is a significant impact.

| username: Billmay表妹 | Original post link

What version are you using?

| username: TiDBer_pkQ5q1l0 | Original post link

6.5.1.

| username: weixiaobing | Original post link

Is there any health check or liveness probe interface running?

| username: GreenGuan | Original post link

Are you sure that this error caused the leader switch?
I looked through previous instances and it seems there was a similar situation, but the bug appears to have been fixed.

| username: xingzhenxiang | Original post link

Take a look at the other two screenshots, we are not the same, and the empty database also reports an error.

| username: GreenGuan | Original post link

If there is no business access, can you turn on the general log to confirm what operation is causing this error?

| username: xingzhenxiang | Original post link

I have business here, CuteRay this is an empty database.

| username: GreenGuan | Original post link

Is there any new feedback on this?

| username: xingzhenxiang | Original post link

Currently, there is no official response yet @ Billmay表妹

| username: tidb狂热爱好者 | Original post link

No problem, just logging, no impact.

| username: xingzhenxiang | Original post link

Are you an official representative or do you have user experience?

| username: liuis | Original post link

I saw earlier that this issue had already been fixed, didn’t it?

| username: xingzhenxiang | Original post link

v6.5.1 is still reporting it, so I’m really scared.