TiDB Coprocessor Read Limit

Translated
1

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

Original topic: tidb Coprocesso读取限制

| username: TiDBer_jQ7mFu99

[Overview]: Long network latency for Coprocessor reads
[Background]: A cluster composed of cloud provider in Beijing, on-premises data center, and overseas nodes. Each location has its own service connecting to the corresponding TiDB.
[Problem]: For example, when making a select request to the on-premises data center, viewing through TiDB dashboard shows that Coprocessor reads are connected to the overseas nodes, causing slow queries. Each table has a small amount of data, and the current bottleneck seems to be the connection to the overseas nodes.
[Version]: v6.1.0

Is there a way to ensure that when the client connects to the on-premises data center, Coprocessor reads are also connected to the on-premises data center, and when the client connects to the overseas nodes, Coprocessor reads are connected to the corresponding overseas nodes?

Tested Placement Rules and as of timestamp in select, but neither solved the problem.

2
| username: ddhe9527 | Original post link

Use Placement Rules to restrict all Region Leaders to domestic data centers.

3
| username: TiDBer_jQ7mFu99 | Original post link

Okay, thank you. I’ll try it first.
But let me ask in advance, will this cause the Coprocessor to connect to domestic data centers when I access services overseas?

4
| username: ddhe9527 | Original post link

It will connect to the domestic network. Your business scenario is more suitable for setting up a separate TiDB cluster in an overseas data center, establishing synchronization with your current cluster through TiCDC. The business in the overseas data center will use another set of TiDB databases, while the domestic business will use your current set.

5
| username: TiDBer_jQ7mFu99 | Original post link

Okay, thank you. I will test it more.

6
| username: system | Original post link

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