Down-peer-region can't recover when enable placement-rule policy #7808
Description
Bug Report
What version of TiKV are you using?
v6.5.3
Steps to reproduce
- set placement-rule:
[
{
"group_id": "pd",
"id": "1",
"start_key": "",
"end_key": "",
"role": "voter",
"is_witness": false,
"count": 2,
"label_constraints": [
{
"key": "disk_type",
"op": "in",
"values": [
"ssd"
]
}
],
"location_labels": [
"host"
],
"isolation_level": "host",
"create_timestamp": 1706696121
},
{
"group_id": "pd",
"id": "2",
"start_key": "",
"end_key": "",
"role": "follower",
"is_witness": false,
"count": 1,
"label_constraints": [
{
"key": "disk_type",
"op": "in",
"values": [
"mix"
]
}
],
"location_labels": [
"host"
],
"isolation_level": "host",
"create_timestamp": 1706696121
}
]
- Start 8 tikv nodes, where 3 nodes are labeled
disk_type=mix, and the other 5 nodes are labeleddisk_type=ssd. Then load data and observe that there is no leader on themixnode, which is expected.
- force scale-in one
mixnode, find there are lots ofdown-peernot recover
- disable placement-rule, then
down-peerstarts to recover
Is this caused by my wrong placement policy or a bug of placement-rule?