[Consultation] Issues with DM Data Source and Worker

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

Original topic: 【咨询】DM 数据源和worker 问题

| username: TiDBer_ZsnVPQB4

[TiDB Usage Environment] Production Environment
[TiDB Version] v.6.5.0
[Reproduction Path] Operations performed that led to the issue
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]
The DM cluster consists of 2 machines in a master-slave configuration.

After adding more than two data sources, there are no available workers. One worker per data source is too wasteful of machines. Without expanding the DM cluster’s dm-workers, is there no way to create a third DM synchronization link?

| username: weixiaobing | Original post link

The data source and work have a one-to-one relationship. If resources are sufficient, you can expand the work on different ports.

| username: xingzhenxiang | Original post link

A single worker can run one task. Deploy DM-Worker nodes based on the number of data sources or synchronization tasks. It is recommended to deploy 1-3 additional idle DM-Worker nodes.