Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: dm 配置
|
username: Raymond
Excuse me, teacher, the pool-size:16 setting in the loaders module of the dm data migration task configuration file should be the number of concurrent threads for dm to import data into the downstream TiDB cluster, right?
This should be the concurrency for full data import into the downstream cluster.
Incremental data # that is, the concurrency for consuming binlog and writing downstream should be the work count under syncer.
I also think it means this: the number of concurrent threads that import the dumped data into the TiDB cluster.
That’s correct. However, please note that if you have two upstreams, each bound to a different DM-worker, then each worker will have 16 connections to TiDB. Therefore, when setting this parameter, you need to consider not only the performance of the machine but also the available connection slots in the downstream TiDB (the same applies to the syncer’s worker count).
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: 
|
username: 
|
username: