Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: table pipeline模块
【TiDB Usage Environment】Production, Testing, Research
【TiDB Version】
In CDC, does the table pipeline in the processor only handle data synchronization for one table?
【Encountered Problem】
【Reproduction Path】What operations were performed to encounter the problem
【Problem Phenomenon and Impact】
【Attachments】
Please provide the version information of each component, such as cdc/tikv, which can be obtained by executing cdc version/tikv-server --version.
In one capture, there can be multiple processors, and each processor can handle one or more tables. Data synchronization for each table is handled by only one table pipeline. Is this the correct understanding?
Is the pipeline here the same principle as Linux anonymous pipes and named pipes?
Is there only one table pipeline for data synchronization of each table? Does one table correspond to one table pipeline, or do multiple tables queue up for one table pipeline? It feels like you need to look at the source code to understand.
Each table should correspond to a table pipeline.
Each table should correspond to a table pipeline.
yes → 专栏 - TiCDC系列分享-02-剖析同步模型与基本架构 | TiDB 社区
This topic will be automatically closed 2 hours after the last reply. No new replies are allowed.
|
username: HACK
|
username: 
|
username: 
|
username: