You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we have many components to simulate the interaction with pd, pd-api-bench, pd-tso-bench, pd-heartbeat-bench, pd-simulator. We can integrate them step by step, with lower learning costs and easier interaction testing of various pd's.
After that we can provide pd the same specification machine to deploy the real pd under the big cluster, simulate the request number of TiDB/TiKV + TiKV heartbeat heartbeat report + all kinds of scheduling for the region and so on.
mock TiKV data to archive the following goals:
can balance region...
can support three forms node: meta-node/simulator(simple raft)/real-tikv
support unified interface to interact with real-tikv
Development Task
pd-api-bench
,pd-tso-bench
,pd-heartbeat-bench
,pd-simulator
. We can integrate them step by step, with lower learning costs and easier interaction testing of various pd's.mock TiKV data to archive the following goals:
mock TiDB&TiKV API
existed tool usages like
./bin/pd-api-bench -http-cases GetRegionStatus-1+1,GetMinResolvedTS-1+1 -client 1 -debug true
mock TiKV heartbeat/TSO
existed tool usages like
./bin/pd-heartbeat-bench --config=./tools/pd-heartbeat-bench/config-template.toml --pd-endpoints http://127.0.0.1:2379
Others
Related
#5468 extend simulator
#6922 extend API bench
The text was updated successfully, but these errors were encountered: