From 3797762e41721bec76d1c88118eee6273ad43f39 Mon Sep 17 00:00:00 2001 From: xixirangrang <35301108+hfxsd@users.noreply.github.com> Date: Thu, 14 Mar 2024 15:17:58 +0800 Subject: [PATCH] removed warning --- sql-statements/sql-statement-admin-bdr-role.md | 4 ---- ticdc/ticdc-bidirectional-replication.md | 4 ---- 2 files changed, 8 deletions(-) diff --git a/sql-statements/sql-statement-admin-bdr-role.md b/sql-statements/sql-statement-admin-bdr-role.md index 4781794542dfa..d13e6400ee108 100644 --- a/sql-statements/sql-statement-admin-bdr-role.md +++ b/sql-statements/sql-statement-admin-bdr-role.md @@ -9,10 +9,6 @@ summary: An overview of the usage of ADMIN [SET|SHOW|UNSET] BDR ROLE for the TiD - Use `ADMIN SHOW BDR ROLE` to show the BDR role of the cluster. - Use `ADMIN UNSET BDR ROLE` to unset the BDR role of the cluster. -> **Warning:** -> -> This feature is experimental. It is not recommended that you use it in the production environment. This feature might be changed or removed without prior notice. If you find a bug, you can report an [issue](https://github.com/pingcap/tidb/issues) on GitHub. - ## Synopsis ```ebnf+diagram diff --git a/ticdc/ticdc-bidirectional-replication.md b/ticdc/ticdc-bidirectional-replication.md index 607f23dda2aae..ac59f389e2456 100644 --- a/ticdc/ticdc-bidirectional-replication.md +++ b/ticdc/ticdc-bidirectional-replication.md @@ -94,10 +94,6 @@ To solve the problem of replicable DDLs and non-replicable DDLs, TiDB introduces When no BDR role is set, you can execute any DDL. But after you set `bdr_mode=true` on TiCDC, the executed DDL will not be replicated by TiCDC. -> **Warning:** -> -> This feature is experimental. It is not recommended that you use it in the production environment. This feature might be changed or removed without prior notice. If you find a bug, you can report an [issue](https://github.com/pingcap/tidb/issues) on GitHub. - ### Replication scenarios of replicable DDLs 1. Choose a TiDB cluster and execute `ADMIN SET BDR ROLE PRIMARY` to set it as the primary cluster.