Skip to content

Commit 8b429d5

Browse files
authored
cdc: remove mention about force-replicate (#19249)
1 parent 9e54e43 commit 8b429d5

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

ticdc/ticdc-overview.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -86,10 +86,6 @@ As shown in the architecture diagram, TiCDC supports replicating data to TiDB, M
8686

8787
- 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.
8888

89-
> **Note:**
90-
>
91-
> Since v4.0.8, TiCDC supports replicating tables without a valid index by modifying the task configuration. However, this compromises the guarantee of data consistency to some extent. For more details, see [Replicate tables without a valid index](/ticdc/ticdc-manage-changefeed.md#replicate-tables-without-a-valid-index).
92-
9389
## Implementation of processing data changes
9490

9591
This section mainly describes how TiCDC processes data changes generated by upstream DML operations.

0 commit comments

Comments
 (0)