9005 Error msg is misleading when tidb is disconnect to one tikv

[mayjiang0203]

When TiDB tries to access the leader of one region, it finds that the tikv cannot be connected. Therefore, it tries to access the tikv nodes where the follower is located. The follower keeps reporting "not leader" and returns not leader error to tidb.
While in tidb log, it reports : error:epoch_not_match:<> , which is misleading.

{"level":"WARN","time":"2024/12/11 17:05:43.014 +00:00","caller":"backoff.go:158","message":"regionMiss backoffer.maxSleep 40000ms is exceeded, errors:\nregion_id:666744652, region_ver:7664971, store_type:tikv, peer_addr:xx.xx.xx.xx:20160, error:epoch_not_match:<>  at 2024-12-11T17:05:41.503977479Z\nregion_id:666744652, region_ver:7664971, store_type:tikv, peer_addr:xx.xx.xx.xx:20160, error:epoch_not_match:<>  at 2024-12-11T17:05:42.007356859Z\nregion_id:666744652, region_ver:7664971, store_type:tikv, peer_addr:xxx.xx.xx.xx:20160, error:epoch_not_match:<>  at 2024-12-11T17:05:42.51108375Z\nlongest sleep type: regionMiss, time: 40010ms"}