Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: 部署一套测试的Tidb集群,各位大佬看看这样可以吗
The table is an initial plan, with 1 PD and TiDB sharing, 3 TiKV, and it’s not yet decided whether to add a new node for monitoring or to share. The character set is default utf8mb4, with two collation rules.
For production use, it is recommended to deploy 3 PDs.
Used in testing, write a test case.
Forgot to mention, the version used is 6.5.4.
Is it feasible for monitoring and PD to share a single node?
If it’s a test environment, there’s no problem at all. Just put the monitoring on the PD and TiDB nodes.
So, should we follow the standardized deployment for this kind of testing environment, instead of using the quick start method?
Just create the cluster normally with your configuration. Tiup playground is only suitable for learning or reproducing specific bug issues.
Hello, may I ask you a question? Can the collation used in TiDB v6.0 and above be changed to MySQL 8.0’s collation? I checked the official documentation but couldn’t find a way to modify it. As shown in the picture, can the default collation of TiDB be changed to utf8mb4_0900_ai_ci?
TiDB does not support the utf8mb4_0900_ai_ci collation.
It’s okay for general testing, but under high load, the TiDB server can’t handle it and needs to be scaled up.
Wait for the new version at the end of the year, it will support MySQL 8 later.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.