ticdc: update best practices (#15494) (#15499)

pingcap · Nov 28, 2023 · 1ed1e31 · 1ed1e31
1 parent 85103ed
commit 1ed1e31
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/ticdc/ticdc-overview.md b/ticdc/ticdc-overview.md
@@ -80,7 +80,7 @@ As shown in the preceding architecture diagram, TiCDC supports replicating data
     - 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 the 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 can be read normally when a disaster occurs in the upstream.
 
 > **Note:**
 >