From 1a416fafe2b708af9d98b9adccb5b78cc88a3d9f Mon Sep 17 00:00:00 2001 From: Aolin Date: Tue, 28 Nov 2023 10:59:52 +0800 Subject: [PATCH 1/2] ticdc: update best practices Signed-off-by: Aolin --- ticdc/ticdc-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ticdc/ticdc-overview.md b/ticdc/ticdc-overview.md index b4c514ffc14f0..060bdf1f61ba1 100644 --- a/ticdc/ticdc-overview.md +++ b/ticdc/ticdc-overview.md @@ -84,7 +84,7 @@ As shown in the architecture diagram, TiCDC supports replicating data to TiDB, M - A primary key (`PRIMARY KEY`) is a valid index. - A unique index (`UNIQUE INDEX`) is valid if every column of the index is explicitly defined as non-nullable (`NOT NULL`) and the index does not have a virtual generated column (`VIRTUAL GENERATED COLUMNS`). -- To use TiCDC in disaster recovery scenarios, you need to configure [redo log](/ticdc/ticdc-sink-to-mysql.md#eventually-consistent-replication-in-disaster-scenarios). +- To ensure eventual consistency when using TiCDC for disaster recovery, you need to configure [redo log](/ticdc/ticdc-sink-to-mysql.md#eventually-consistent-replication-in-disaster-scenarios) and ensure that the storage system where the redo log is written remains accessible when a disaster occurs in the upstream. ## Unsupported scenarios From b69cc38839802003a6bc45b2e500a53a8f2fe125 Mon Sep 17 00:00:00 2001 From: Aolin Date: Tue, 28 Nov 2023 14:22:52 +0800 Subject: [PATCH 2/2] refine wording Co-authored-by: Lilian Lee --- ticdc/ticdc-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ticdc/ticdc-overview.md b/ticdc/ticdc-overview.md index 060bdf1f61ba1..bd881e72885d1 100644 --- a/ticdc/ticdc-overview.md +++ b/ticdc/ticdc-overview.md @@ -84,7 +84,7 @@ As shown in the architecture diagram, TiCDC supports replicating data to TiDB, M - A primary key (`PRIMARY KEY`) is a valid index. - A unique index (`UNIQUE INDEX`) is valid if every column of the index is explicitly defined as non-nullable (`NOT NULL`) and the index does not have a virtual generated column (`VIRTUAL GENERATED COLUMNS`). -- To ensure eventual consistency when using TiCDC for disaster recovery, you need to configure [redo log](/ticdc/ticdc-sink-to-mysql.md#eventually-consistent-replication-in-disaster-scenarios) and ensure that the storage system where the redo log is written remains accessible when a disaster occurs in the upstream. +- To ensure eventual consistency when using TiCDC for disaster recovery, you need to configure [redo log](/ticdc/ticdc-sink-to-mysql.md#eventually-consistent-replication-in-disaster-scenarios) and ensure that the storage system where the redo log is written can be read normally when a disaster occurs in the upstream. ## Unsupported scenarios