Hybrid deployment practice of TiDB cluster in production environment

1. Background Due to various off-site factors, we cannot freely choose the ideal hardware environment, and the current hardware configuration of a single physical machine is often higher than the demand. In order to plan resources more reasonably In many cases, a server cannot “luxury” deploy only one instance, but will consider deploying TiDB or TiKV on a single machine with multiple instances. This requires building a highly available and high-performance TiDB cluster as much as possible in the existing environment. This article mainly shares the process of hybrid deployment of TiDB clusters in an actual production environment for your reference. 2. Hardware configuration 10 physical machines, each with 56C 384G 4 pieces of 2TB NVME hard disk. Monitoring, HA and other machines can use virtual machines, so they are not included in the purchase budget. The configuration is up to standard, but due to various factors, it was originally expected that the hardware of one cluster would need to be mixed and deployed with two sets of clusters. 3. Cluster topology planning Cluster 1 Instance IP TiDB & PD 10.0.0.1 TiDB & PD 10.0.0.2 PD 10.0.0.3 10.0.0.4 Tikv *2 10.0.0.5 Tikv *2 10.0.0.6 Tikv *2 10.0.0.7 Tikv *2 10.0.0.8…