Skip to content

ticdc: update best practices (#15516) #15521

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 28, 2023
Merged

ticdc: update best practices (#15516) #15521

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1be53ae
This is an automated cherry-pick of #15516
Oreoxmt Nov 28, 2023
b51fbb0
resolve conflicts
Oreoxmt Nov 28, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ticdc/ticdc-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ TiCDC 作为 TiDB 的增量数据同步工具，通过 PD 内部的 etcd 实现
- 主键 (`PRIMARY KEY`) 为有效索引。
- 唯一索引 (`UNIQUE INDEX`) 中每一列在表结构中明确定义非空 (`NOT NULL`) 且不存在虚拟生成列 (`VIRTUAL GENERATED COLUMNS`)。

- 容灾场景下使用 TiCDC 需要配置 [redo log](/ticdc/ticdc-sink-to-mysql.md#灾难场景的最终一致性复制) 实现最终一致性。
- 在使用 TiCDC 实现容灾的场景下，为实现最终一致性，需要配置 [redo log](/ticdc/ticdc-sink-to-mysql.md#灾难场景的最终一致性复制) 并确保 redo log 写入的存储系统在上游发生灾难时可以正常读取。
- 使用 TiCDC 同步单行较大 (> 1k) 的宽表时，推荐设置 TiCDC 参数 [per-table-memory-quota](/ticdc/ticdc-server-config.md)，使得 `per-table-memory-quota` = `ticdcTotalMemory` / (`tableCount` * 2)。`ticdcTotalMemory` 是一个 TiCDC 节点的内存，`tableCount` 是一个 TiCDC 节点同步的目标表的数量。

### 暂不支持的场景
Expand Down