Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: DM集群创建第二个数据源报错 ‘no mysql source is being handled in the worker’
[TiDB Usage Environment]
Production Environment
[TiDB Version]
7.5.1
[Reproduction Path]
Error when creating data source
[Encountered Problem: Problem Phenomenon and Impact]
Error during creation: no mysql source is being handled in the worker
Confirm whether your DM configuration file is correct.
Check for syntax errors or missing configurations.
The configuration file is in the screenshot. I copied the first successfully created configuration and modified the data source address.
Solution can be found in the international community: Failed to create upstream datasource
After reading the article posted by the user above, the content is roughly:
Reason: It was found that the dm-worker node takes more than 10 seconds to attempt to connect to the upstream MySQL server.
Solution: The issue was resolved by optimizing the connection between dm-worker and MySQL.
Follow up on the subsequent solutions.
|
username: TiDBer_zzZPx7Nd
|
username: 
|
username: 
|
username: