Is it considered a bug when TiDB reports "write: connection reset by peer" after configuring load balancing health checks, and how should the health checks be configured to avoid this error?

Translated
1

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

Original topic: 配置了负载均衡健康检查tidb报 write: connection reset by peer 这种问题算BUG吗，这么配健康检查才不报着错误

| username: ffeenn

[TiDB Usage Environment] Production Environment
[TiDB Version] v5.4.1
[Encountered Problem]
tidb组件大量报错：write: connection reset by peer - TiDB 的问答社区 Is this issue where TiDB reports “write: connection reset by peer” when load balancing health checks are configured considered a bug? Configuring health checks this way avoids the error. Besides increasing the log volume, what other impacts might this continuous error reporting have?

image
image1200×387 20 KB

2
| username: db_user | Original post link

How about checking out the official expert articles? Would that be helpful?
https://asktug.com/t/topic/182953

3
| username: ffeenn | Original post link

This doesn’t matter, it doesn’t have any impact, right?

4
| username: db_user | Original post link

It seems that there should be no other impact besides large logs, it should just be caused by the proxy health check.

5
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.