Get desktop application:
View/edit binary Protocol Buffers messages
GetMembers get the member list of this cluster. It does not require the cluster_id in request matchs the id of this cluster.
Do NOT return tombstone stores if set to true.
Leader Peer sending the heartbeat.
Pending peers are the peers that the leader can't consider as working followers.
Approximate region size.
Notice, Scheduleeer only allows handling reported epoch >= current scheduler's. Leader peer reports region status with RegionHeartbeatRequest to scheduler regularly, scheduler will determine whether this region should do ChangePeer or not. E,g, max peer number is 3, region A, first only peer 1 in A. 1. Scheduler region state -> Peers (1), ConfVer (1). 2. Leader peer 1 reports region state to scheduler, scheduler finds the peer number is < 3, so first changes its current region state -> Peers (1, 2), ConfVer (1), and returns ChangePeer Adding 2. 3. Leader does ChangePeer, then reports Peers (1, 2), ConfVer (2), scheduler updates its state -> Peers (1, 2), ConfVer (2). 4. Leader may report old Peers (1), ConfVer (1) to scheduler before ConfChange finished, scheduler stills responses ChangePeer Adding 2, of course, we must guarantee the second ChangePeer can't be applied in TiKV.
Scheduler can return transfer_leader to let TiKV does leader transfer itself.
ID of the region
Leader of the region at the moment of the corresponding request was made.
no limit when limit <= 0.
end_key is +inf when it is empty.
We split the region into two, first uses the origin parent region id, and the second uses the new_region_id. We must guarantee that the new_region_id is global unique.
The peer ids for the new split region.
Scheduler will use these region information if it can't find the region. For example, the region is just split and hasn't report to Scheduler yet.
Used in:
Used in:
Used in:
Used as request type in: Scheduler.GetPrevRegion, Scheduler.GetRegion
Used as response type in: Scheduler.GetPrevRegion, Scheduler.GetRegion, Scheduler.GetRegionByID
Used in:
name is the name of the Scheduler member.
member_id is the unique id of the Scheduler member.
Used in:
Used in:
Used in:
, , , , , , , , , , , , , , , , , , , ,cluster_id is the ID of the cluster which be sent to.
Used in:
, , , , , , , , , , , , , , , , , , ,cluster_id is the ID of the cluster which sent the response.
Used in:
,Capacity for the store.
Available size for the store.
Total region count in this store.
Current sending snapshot count.
Current receiving snapshot count.
When the store is started (unix timestamp in seconds).
How many region is applying snapshot.
If the store is busy
Actually used space by db
Actually reported time interval
Threads' CPU usages in the store
Threads' read disk I/O rates in the store
Threads' write disk I/O rates in the store
Operations' latencies in the store
Used in:
The unix timestamp in seconds of the start of this period.
The unix timestamp in seconds of the end of this period.
Used in:
Used in: