[INFO] [kv.rs:1117] ["call CheckLeader failed"] [address=ipv4:10.114.26.103:64854] [err=Grpc(RemoteStopped)]

Translated
1

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

Original topic: [INFO] [kv.rs:1117] [“call CheckLeader failed”] [address=ipv4:10.114.26.103:64854] [err=Grpc(RemoteStopped)]

| username: 奋斗的大象

[TiDB Usage Environment] Production Environment
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachment: Screenshot/Log/Monitoring] Original BUG

2
| username: 像风一样的男子 | Original post link

What are you asking?

3
| username: redgame | Original post link

Check whether the network connection between TiKV nodes is stable, and ensure that there are no network failures, packet loss, or high latency.

4
| username: songxuecheng | Original post link

Can be ignored, does not affect the cluster.

5
| username: zhanggame1 | Original post link

Just ignore the info; it’s normal to not find the leader. If the leader has migrated and TiDB has cached the leader’s position, it won’t be able to find it. In this case, TiDB will go to PD to recheck the leader’s position.

6
| username: Kongdom | Original post link

Is it a duplicate topic? If the INFO information shows that the cluster status is normal after checking, it can be ignored. Errors need to be paid close attention to.

7
| username: Billmay表妹 | Original post link

【TiDB Version】
【Reproduction Path】What operations were performed when the issue occurred
【Encountered Issue: Issue Phenomenon and Impact】
【Resource Configuration】Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page

Please provide more information~