Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: PD元数据
|
username: TiDBer_fiJaQjDR
Could you please help reply with what metadata is stored by PD?
|
username: TiDBer_fiJaQjDR
|
username: 
|
username: - PD divides the entire data into a series of Regions based on the size of the data, with each Region carrying a smaller range of the entire data. PD maintains the following metadata for each Region:
{
“id”: 10001,
“start_key”: “xxx”,
“end_key”: “yyy”,
“epoch”: {
“conf_ver”: 50,
“version”: 268
},
“peers”: [
{
"id": 7820688,
“store_id”: 7583502
}, {“id”: 9147810,
“store_id”: 7586672
}, {“id”: 9186477,
“store_id”: 7584594
} ], “leader”: { “id”: 7820688, “store_id”: 7583502 }, “written_bytes”: 15639, “read_bytes”: 236, “approximate_size”: 515, “approximate_keys”: 4747086 }
|
username: Partition information of the table, number of replicas, replica locations, etc.
PD stores TiKV’s routing information and region information, while the table schema and other metadata are stored by TiKV itself.
The metadata information about the Schema should be stored by TiKV itself.
|
username: You can connect to the PD command line yourself and take a look
tiup ctl:{$CLUSTER_VERSION} pd -u 10.0.XXX.XXX:2379 -i
I can’t view images directly. Please provide the text you need translated.
|
username: 
|
username: 
|
username: The metadata of the entire TiKV cluster
Allocation of global IDs and transaction IDs
Global TSO
Collection of cluster information
Dashboard
|
username: In PD, it should store TiKV node information, Region information, and raft group information.
|
username: You can view the stored metadata details through the API.
|
username: Global ID and transaction ID, global TSO, cluster information
|
username: The metadata of the entire TiKV cluster, allocation of global IDs and transaction IDs, global TSO, collection of cluster information, dashboard.
|
username: 
|
username: You see, many tools require providing the PD address, which indicates that they either fetch metadata from PD or update PD metadata.