Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: TIdb 4.0版本的DM工具使用 最新版会有问题吗？还是用5.0版本比较好
Is there any problem using the latest version of the DM tool in TiDB 4.0? Or is it better to use version 5.0, which is closer to the TiDB version?
How to keep the versions of DM and DMCTL consistent? The version numbers of the two are different, and they are installed together as dm and dmctl during installation. If I specify dmctl 5.3.0, what is the corresponding version of dm, and how can I check it?
If there is no need for new version features, it is recommended to use the same version as the cluster.
DM does not have a 4.0 version. After 2.0, it went straight to 5.3.
Before cluster version v5.3, it corresponded to DM version 2.0. Starting from v5.3, the cluster version and DM version have been unified to the same version number. Therefore, using DM 2.0 for a 4.0 cluster should be sufficient, but it is still recommended to upgrade the cluster version as soon as possible.
It’s recommended to use the DM version that matches your TiDB version.
If these two versions don’t match, there might be some strange bugs.
Now there is a problem that dmctl follows the major version number, but the version of dm listed by tiup starts with 1, which is different from the major version.
How should this be handled?
For DM, use version 2.0. For dmctl, just find one that was released around the same time as the DM release.
Do the tools also need to match the version? tiup install dm dmctl is for installing the tools. tiup dm deploy dm-test v5.3.0 ./topology.yaml --user root -p is for deploying the DM cluster. The tools don’t need to be an old version, right? Only the DM cluster version needs to match the corresponding old version during deployment, correct?
It’s normal, these two are inconsistent. Just ensure that the dmctl version is consistent with the dm-worker/dm-master version, and the dm-worker/dm-master version is consistent with the TiDB version.
The versions might be different, but it’s best to test it.
Well, theoretically the tool is backward compatible, so using the new version of the tool shouldn’t be a problem.
I tried it and found that the dm and dmctl components cannot select a version. Using tiup install dm dmctl and adding a version at the end doesn’t work and fails. It can only install the latest version. Installing the dm cluster allows selecting the corresponding old version. Currently, my components are version 7.3. Installing DM cluster version 5.3, TiDB is version 4.0.2 -_-||
When deploying with tiup dm, you can specify the version of the dm cluster to be deployed.
Regarding this, I know it’s the cluster version. I’m asking if the component version has any impact. For example, “tiup install dm dmctl”.
tiup install dmctl:v4.0.0
You didn’t specify the subversion number, so I gave you .0 as the subversion number. You need to pay attention to this. The DM version and dmctl are inconsistent, but since it’s used for deployment, it doesn’t really matter.
This way, you can roughly unify to a single version.
Well, I will use version 7.3 for the components. Just specify the version when deploying the DM cluster. There are no issues with the test results now. Synchronizing MySQL 5.7.32 with DM 5.3 to TiDB 4.0.2 works fine.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: 舞动梦灵
|
username: 
|
username: 
|
username: 
|
username: