Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: 数据同步方案
|
username: ffeenn
[Test Environment for TiDB]
[TiDB Version] 5.4.1
[Reproduction Path]
[Encountered Issues: Problem Phenomenon and Impact]
TiDB 5.4.1 => PolarDB-X1
When the downstream database is PolarDB-X1, what are some convenient and constructive solutions for full and incremental data synchronization?
TiDB currently does not have such a tool. You can check if PolarDB has it, or try flink-cdc.
The most convenient way is to directly use ETL tools, such as Kettle, which can be used and written as needed and supports heterogeneous databases.
You’re right, I’m testing this now. After running it, I feel like it could crash at any moment, haha. Maybe I’m still not familiar with this thing. Now I just want to ask everyone to test and screen the tools they’ve used.
We’ve been using it for quite a while. The only issue is that things made with Java consume too much memory. Other than that, we haven’t found any problems.
In fact, TiCDC can do it. TiDB’s data can be sent to Kafka through TiCDC, and then the sink end can write to anywhere.
Curve-saving the nation: TiDB → TiCDC → MySQL → CloudCanal/Seatunnel/DTS → PolarDB
Yes, there are compatibility issues, and quite a few changes have been made, so I want to try using other DM or ETL tools.
If the number of links is not long enough, how can it be called a roundabout way to save the country?
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: