missing leader如何处理

【版本】5.2.3 arm
【问题】
tikv日志报:
[2022/09/10 22:03:53.051 +08:00] [WARN] [peer.rs:4082] ["leader missing longer than max_leader_missing_duration. To check with pd and other peers whether it's still valid"] [expect=2h] [**peer_id=1672003177] [region_id=1659059842]**

这些 missing leader 该如何处理?

$ pd-ctl region 1659059842
{
“id”: 1659059842,
“start_key”: “748000000000007EFFB95F728000000026FF07F87D0000000000FA”,
“end_key”: “748000000000007EFFB95F728000000026FF093D7B0000000000FA”,
“epoch”: {
“conf_ver”: 72629,
“version”: 127640
},
“peers”: [
{
“id”: 1659059843,
“store_id”: 2,
“role_name”: “Voter”
},
{
“id”: 1659059844,
“store_id”: 1561469454,
“role_name”: “Voter”
},
{
“id”: 1659059845,
“store_id”: 11107291,
“role_name”: “Voter”
}
],
“leader”: {
“id”: 1659059844,
“store_id”: 1561469454,
“role_name”: “Voter”
},
“written_bytes”: 1523,
“read_bytes”: 0,
“written_keys”: 2,
“read_keys”: 0,
“approximate_size”: 3,
“approximate_keys”: 81920
}

image

region显示没有表,表是否真的不存在了?
image

region 是丢了leader,还是所有的副本都丢了,只剩下元数据了?

所有的副本全丢了,就可以直接将元数据移除掉了…

某个peer被raft group无情的抛弃了,无组织无领导了

可以清理掉了… 标准的垃圾数据了 :custard:

这个数据咋产生的?

WARN级别的日志,没有影响吧?做了什么操作导致的呢?