# 案例 B：频繁产生调度-问题定位
```
“store”: {
“id”: 5,
“address”: “172.18.69.175:20160”,
“version”: “3.0.12”,
“state_name”: “Up”
},
“status”: {
“capacity”: “6.93TiB”,
“available”: “2.98TiB”,
“leader_count”: 25254,
“leader_weight”: 1,
“leader_score”: 5341269,
“leader_size”: 5341269,
“region_count”: 79246,
“region_weight”: 1,
“region_score”: 16702847,
“region_size”: 16702847,
“sending_snap_count”: 1,
“start_ts”: “2020-12-09T21:34:20+08:00”,
“last_heartbeat_ts”: “2020-12-21T10:35:13.728533086+08:00”,
“uptime”: “277h0m53.728533086s”
}
},
{
```

------------------------------------------------------------
leader-schedule-policy:用于选择 Leader 的调度策略，可以选择按照 size 或者 count 来进行调度。

region-weight

leader-weight

leader-weight 和 region-weight 分别用于控制 Leader 权重以及 Region 权重（默认值都为 “1”）。假如把某个 Store 的 leader-weight 设为 “2”，调度稳定后，则该节点的 Leader 数量约为普通节点的 2 倍；假如把某个 Store 的 region-weight 设为 “0.5”，那么调度稳定后该节点的 Region 数量约为其他节点的一半。