Skip to content
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

ticdc: adjust TOC and reorganize troubleshooting & faq #9945

Merged
merged 9 commits into from
Jun 27, 2022
Merged

ticdc: adjust TOC and reorganize troubleshooting & faq #9945

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
b149105
ticdc: split troubleshoot-ticdc.md into two docs
shichun-0415 Jun 21, 2022
ebecf53
fix links
shichun-0415 Jun 21, 2022
dd0dca4
fix CI
shichun-0415 Jun 22, 2022
d9a8453
Update TOC.md
shichun-0415 Jun 27, 2022
bef0e0d
*: improve TiCDC TOC and fix format
lilin90 Jun 27, 2022
50060ca
fix format
shichun-0415 Jun 27, 2022
2a5808e
Update TOC.md
shichun-0415 Jun 27, 2022
7e40ff9
Apply suggestions from code review
shichun-0415 Jun 27, 2022
cb388eb
add ticdc in title
shichun-0415 Jun 27, 2022
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
12 changes: 7 additions & 5 deletions TOC.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -484,13 +484,15 @@
- [概述](/ticdc/ticdc-overview.md)
- [安装部署](/ticdc/deploy-ticdc.md)
- [运维管理](/ticdc/manage-ticdc.md)
- [故障诊断](/ticdc/troubleshoot-ticdc.md)
- [故障处理](/ticdc/troubleshoot-ticdc.md)
- [常见问题解答](/ticdc/ticdc-faq.md)
- [监控指标](/ticdc/monitor-ticdc.md)
- [报警规则](/ticdc/ticdc-alert-rules.md)
- [TiCDC Open API](/ticdc/ticdc-open-api.md)
- [TiCDC Open Protocol](/ticdc/ticdc-open-protocol.md)
- [TiCDC Canal-JSON Protocol](/ticdc/ticdc-canal-json.md)
- [TiCDC Avro Protocol](/ticdc/ticdc-avro-protocol.md)
- [参考指南]
- [TiCDC Open API](/ticdc/ticdc-open-api.md)
- [TiCDC Open Protocol](/ticdc/ticdc-open-protocol.md)
- [TiCDC Canal-JSON Protocol](/ticdc/ticdc-canal-json.md)
- [TiCDC Avro Protocol](/ticdc/ticdc-avro-protocol.md)
- [将 TiDB 集成到 Confluent Platform](/ticdc/integrate-confluent-using-ticdc.md)
- [术语表](/ticdc/ticdc-glossary.md)
- TiUniManager
Expand Down
2 changes: 1 addition & 1 deletion _index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ aliases: ['/docs-cn/dev/','/docs-cn/','/docs-cn/stable/']
- [SQL 诊断](/information-schema/information-schema-sql-diagnostics.md)
- [热点问题处理](/troubleshoot-hot-spot-issues.md)
- [磁盘 I/O 过高](/troubleshoot-high-disk-io.md)
- [TiCDC 常见问题](/ticdc/troubleshoot-ticdc.md)
- [TiCDC 故障处理](/ticdc/troubleshoot-ticdc.md)
- [TiFlash 常见问题](/tiflash/troubleshoot-tiflash.md)

</NavColumn>
Expand Down
3 changes: 2 additions & 1 deletion faq/migration-tidb-faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,8 @@ aliases: ['/docs-cn/dev/faq/migration-tidb-faq/']
- [TiDB Binlog 常见问题](/tidb-binlog/tidb-binlog-faq.md)
- [TiDB Lightning 常见问题](/tidb-lightning/tidb-lightning-faq.md)
- [Data Migration 常见问题](/dm/dm-faq.md)
- [TiCDC 常见问题和故障处理](/ticdc/troubleshoot-ticdc.md)
- [TiCDC 常见问题](/ticdc/ticdc-faq.md)
- [TiCDC 故障处理](/ticdc/troubleshoot-ticdc.md)

## 全量数据导出导入

Expand Down
2 changes: 1 addition & 1 deletion migrate-from-tidb-to-tidb.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -236,7 +236,7 @@ aliases: ['/zh/tidb/dev/incremental-replication-between-clusters/']

3. 重新开启 GC。

TiCDC 可以保证 GC 只回收已经同步的历史数据。因此，创建完从上游到下游集群的 changefeed 之后，就可以执行如下命令恢复集群的垃圾回收功能。详情请参考 [TiCDC GC safepoint 的完整行为](/ticdc/troubleshoot-ticdc.md#ticdc-gc-safepoint-的完整行为是什么)。
TiCDC 可以保证 GC 只回收已经同步的历史数据。因此，创建完从上游到下游集群的 changefeed 之后，就可以执行如下命令恢复集群的垃圾回收功能。详情请参考 [TiCDC GC safepoint 的完整行为](/ticdc/ticdc-faq.md#ticdc-gc-safepoint-的完整行为是什么)。

{{< copyable "sql" >}}

Expand Down
3 changes: 2 additions & 1 deletion production-deployment-using-tiup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -449,4 +449,5 @@ tiup cluster display tidb-test
如果你已同时部署了 [TiCDC](/ticdc/ticdc-overview.md)，接下来可参阅以下文档：

- [TiCDC 任务管理](/ticdc/manage-ticdc.md)
- [TiCDC 常见问题](/ticdc/troubleshoot-ticdc.md)
- [TiCDC 常见问题](/ticdc/ticdc-faq.md)
- [TiCDC 故障处理](/ticdc/troubleshoot-ticdc.md)
2 changes: 1 addition & 1 deletion replicate-between-primary-and-secondary-clusters.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -255,7 +255,7 @@ summary: 了解如何配置一个 TiDB 集群以及该集群的 TiDB 或 MySQL

3. 重新开启 GC。

TiCDC 可以保证未同步的历史数据不会被回收。因此，创建完从上游到下游集群的 changefeed 之后，就可以执行如下命令恢复集群的垃圾回收功能。详情请参考 [TiCDC GC safepoint 的完整行为](/ticdc/troubleshoot-ticdc.md#ticdc-gc-safepoint-的完整行为是什么)。
TiCDC 可以保证未同步的历史数据不会被回收。因此，创建完从上游到下游集群的 changefeed 之后，就可以执行如下命令恢复集群的垃圾回收功能。详情请参考 [TiCDC GC safepoint 的完整行为](/ticdc/ticdc-faq.md#ticdc-gc-safepoint-的完整行为是什么)。

{{< copyable "sql" >}}

Expand Down
2 changes: 1 addition & 1 deletion ticdc/deploy-ticdc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ cdc server --pd=http://10.0.10.25:2379 --log-file=ticdc_3.log --addr=0.0.0.0:830
- `pd`：TiCDC 监听的 PD 节点地址，用 `,` 来分隔多个 PD 节点地址。
- `config`：可选项，表示 TiCDC 使用的配置文件地址。TiCDC 从 v5.0.0 开始支持该选项，TiUP 从 v1.4.0 开始支持在部署 TiCDC 时使用该配置。
- `data-dir`：指定 TiCDC 使用磁盘储存文件时的目录。目前 Unified Sorter 会使用该目录储存临时文件，建议确保该目录所在设备的可用空间大于等于 500 GiB。更详细的说明参见 [Unified Sorter](/ticdc/manage-ticdc.md#unified-sorter-功能)。对于使用 TiUP 的用户，本选项可以通过配置 [`cdc_servers`](/tiup/tiup-cluster-topology-reference.md#cdc_servers) 中的 `data_dir` 来指定或默认使用 `global` 中 `data_dir` 路径。
- `gc-ttl`：TiCDC 在 PD 设置的服务级别 GC safepoint 的 TTL (Time To Live) 时长，和 TiCDC 同步任务所能够停滞的时长。单位为秒，默认值为 `86400`，即 24 小时。注意：TiCDC 同步任务的停滞会影响 TiCDC GC safepoint 的推进，即会影响上游 TiDB GC 的推进，详情可以参考 [TiCDC GC safepoint 的完整行为](/ticdc/troubleshoot-ticdc.md#ticdc-gc-safepoint-的完整行为是什么)。
- `gc-ttl`：TiCDC 在 PD 设置的服务级别 GC safepoint 的 TTL (Time To Live) 时长，和 TiCDC 同步任务所能够停滞的时长。单位为秒，默认值为 `86400`，即 24 小时。注意：TiCDC 同步任务的停滞会影响 TiCDC GC safepoint 的推进，即会影响上游 TiDB GC 的推进，详情可以参考 [TiCDC GC safepoint 的完整行为](/ticdc/ticdc-faq.md#ticdc-gc-safepoint-的完整行为是什么)。
- `log-file`：TiCDC 进程运行时日志的输出地址，未设置时默认为标准输出 (stdout)。
- `log-level`：TiCDC 进程运行时的日志级别，默认为 `"info"`。
- `ca`：TiCDC 创建 TLS 连接时使用的 CA 证书文件路径，PEM 格式，可选。
Expand Down
2 changes: 1 addition & 1 deletion ticdc/ticdc-alert-rules.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -181,7 +181,7 @@ summary: 了解 TiCDC 集群监控报警规则以及处理方法。

* 处理方法：

MySQL 报错的情况较多，参考[`TiCDC 常见问题和故障处理`](/ticdc/troubleshoot-ticdc.md)。
MySQL 报错的情况较多，参考[`TiCDC 故障处理`](/ticdc/troubleshoot-ticdc.md)。

### `ticdc_memory_abnormal`

Expand Down
Loading