我的书签
添加书签
移除书签TiFlash Deployment Topology
This document describes the deployment topology of TiFlash based on the minimal TiDB topology.
TiFlash is a columnar storage engine, and gradually becomes the standard cluster topology. It is suitable for real-time HTAP applications.
Topology information
| Instance | Count | Physical machine configuration | IP | Configuration |
|---|---|---|---|---|
| TiDB | 3 | 16 VCore 32GB 1 | 10.0.1.7 10.0.1.8 10.0.1.9 | Default port Global directory configuration |
| PD | 3 | 4 VCore 8GB 1 | 10.0.1.4 10.0.1.5 10.0.1.6 | Default port Global directory configuration |
| TiKV | 3 | 16 VCore 32GB 2TB (nvme ssd) 1 | 10.0.1.1 10.0.1.2 10.0.1.3 | Default port Global directory configuration |
| TiFlash | 1 | 32 VCore 64 GB 2TB (nvme ssd) 1 | 10.0.1.11 | Default port Global directory configuration |
| Monitoring & Grafana | 1 | 4 VCore 8GB * 1 500GB (ssd) | 10.0.1.10 | Default port Global directory configuration |
Topology templates
For detailed descriptions of the configuration items in the above TiDB cluster topology file, see Topology Configuration File for Deploying TiDB Using TiUP.
Key parameters
- To enable the Placement Rules feature of PD, set the value of
replication.enable-placement-rulesin the configuration template totrue. - The instance level
"-host"configuration intiflash_serversonly supports IP, not domain name. - For detailed TiFlash parameter description, see TiFlash Configuration.
Note
- You do not need to manually create the
tidbuser in the configuration file. The TiUP cluster component automatically creates thetidbuser on the target machines. You can customize the user, or keep the user consistent with the control machine. - If you configure the deployment directory as a relative path, the cluster will be deployed in the home directory of the user.
