DM did not start the worker

Chinese Translated
1

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

Original topic: dm没有启动worker

| username: 宸凡_22

[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]
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots / Logs / Monitoring]

image
image1380×202 85.4 KB

image
image1380×934 179 KB

2
| username: 宸凡_22 | Original post link

The configuration file is used to change the database name from xms to xms62 during the import process.

3
| username: dba远航 | Original post link

The second picture is unclear.

4
| username: 宸凡_22 | Original post link

********* Task Information Configuration *********

name: dm62 # Task name, must be globally unique
task-mode: all

******** Data Source Configuration **********

mysql-instances:

  • source-id: “mysql-62” # Migrate data from data source with source-id = mysql-replica-01
    block-allow-list: “bw-rule-1”
    filter-rules: [“filter-rule-1”]
    route-rules: [“route-rule-1”]

******** Target TiDB Configuration **********

target-database: # Target TiDB configuration
host: “10.11.26.53”
port: 4000
user: “zkjt”
password: “0yohIwDApewdm32c4vdPokDkVGqtuf1RzU6n/A6Y=” # If the password is not empty, it is recommended to use the encrypted ciphertext through dmctl

block-allow-list:
bw-rule-1:
do-dbs: [“xms”]
do-tables:
- db-name: “xms”
tbl-name: “*”

filters:
filter-rule-1:
schema-pattern: “xms”
events: [“truncate table”,“drop table”]
action: Ignore

routes:
route-rule-1:
schema-pattern: “xms”
table-pattern: “"
target-schema: “xms62”
target-table: "”

5
| username: 有猫万事足 | Original post link

tiup dm display <dm-cluster-name>

Check the result.
I feel that when you deployed the DM cluster, either you didn’t deploy the dm-worker nodes, or all the existing dm-workers are bound to data sources and there are no free dm-workers available for binding. You need to scale out the dm-worker nodes.

6
| username: 宸凡_22 | Original post link

The image you provided is not accessible. Please provide the text you need translated.

7
| username: 有猫万事足 | Original post link

You need to create a source and then start the task.

8
| username: 小龙虾爱大龙虾 | Original post link

You should check the logs of the dm-master node. The screenshot you posted doesn’t show any errors at all.

9
| username: wangccsy | Original post link

How to determine it.

10
| username: 宸凡_22 | Original post link

dm-master.log (53.7 KB)

11
| username: 有猫万事足 | Original post link

The permissions are not set correctly.
lack of REPLICATION CLIENT privilege;
lack of Select privilege: {INFORMATION_SCHEMA};
lack of RELOAD privilege;

The error is due to these 3 permissions.

You should check the actual permissions used against the documentation, as there might be some missing.

12
| username: dba远航 | Original post link

“lack of REPLICATION CLIENT privilege;”] Feels like a user privilege issue.

13
| username: 宸凡_22 | Original post link

There is no response when starting. Are there any restrictions on using DM? I checked the documentation:

  • MySQL version 5.5 ~ 5.7
    Note:
    If the upstream MySQL/MariaDB servers form a master-slave replication structure, the MySQL version needs to be higher than 5.7.1 or the MariaDB version needs to be equal to or higher than 10.1.3.
    The current database versions in use are all 5.7.35 and above.

Are there any other restrictions?