Network Latency Requirements Between TiDB Components

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: tidb组件之间网络延迟要求

| username: TiDBer_yUoxD0vR

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
What is the network latency requirement between TiDB components? The network latency between our data center and Alibaba Cloud machines is 4ms. Can they be mixed?
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots / Logs / Monitoring]

| username: xingzhenxiang | Original post link

TiDB has high bandwidth requirements.

Network latency should be acceptable. Check out this test:

| username: tidb菜鸟一只 | Original post link

It is not recommended to mix deployments like this. If you want to migrate to Alibaba Cloud, you can directly use TiCDC, which has basically no impact on local business. After signing the application, you can directly switch the address.

| username: TiDBer_yUoxD0vR | Original post link

The method of deploying a new cluster is not feasible for our actual situation. We want to migrate to Alibaba Cloud by adding and removing nodes.

| username: zhanggame1 | Original post link

Why not just copy it? Set up a cluster on Alibaba Cloud and synchronize it to achieve consistency.

| username: 孤君888 | Original post link

4ms is already very low, it can basically be considered as a large intranet. You can test it first and see, it doesn’t seem to be a big problem.

| username: liuis | Original post link

4ms is almost no latency…

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.