From 84b33f4520872c5467760ffd79085a34db2e254a Mon Sep 17 00:00:00 2001 From: ti-srebot <66930949+ti-srebot@users.noreply.github.com> Date: Fri, 16 Oct 2020 16:19:00 +0800 Subject: [PATCH] cherry pick #4074 to release-4.0 (#4075) Signed-off-by: ti-srebot Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com> --- ticdc/manage-ticdc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ticdc/manage-ticdc.md b/ticdc/manage-ticdc.md index 49065462cb1e8..40c8f7c40cc56 100644 --- a/ticdc/manage-ticdc.md +++ b/ticdc/manage-ticdc.md @@ -685,7 +685,7 @@ To use the cyclic replication feature, you need to configure the following param + `--cyclic-replica-id`: Specifies the data source (to be written) ID of the upstream cluster. Each cluster ID must be unique. + `--cyclic-filter-replica-ids`: Specifies the data source ID to be filtered, which is usually the downstream cluster ID. -+ `--cyclic-sync-ddl`: Determines whether to replicate DDL statements to the downstream. DDL replication can only be enabled in the TiCDC component of one cluster. ++ `--cyclic-sync-ddl`: Determines whether to replicate DDL statements to the downstream. To create a cyclic replication task, take the following steps: