TiCDC scale out: experimental feature (pingcap#12490)

hfxsd · Feb 14, 2023 · f212f32 · f212f32
1 parent 6dde450
commit f212f32
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 4 deletions.
diff --git a/ticdc/ticdc-changefeed-config.md b/ticdc/ticdc-changefeed-config.md
@@ -92,8 +92,9 @@ ignore-insert-value-expr = "price > 1000 and origin = 'no where'" # Ignore inser
 [scheduler]
 # Splits a table into multiple replication ranges based on the number of Regions, and these ranges can be replicated by multiple TiCDC nodes.
 # Note:
-# 1. This parameter only takes effect on Kafka changefeeds and is not supported on MySQL changefeeds.
-# 2. TiCDC does not split tables with fewer Regions than this parameter value into multiple replication ranges.
+# 1. Scaling out a single large table is an experimental feature. It is not recommended that you use it in the production environment.
+# 2. This parameter only takes effect on Kafka changefeeds and is not supported on MySQL changefeeds.
+# 3. TiCDC does not split tables with fewer Regions than this parameter value into multiple replication ranges.
 # region-per-span = 50000
 
 [sink]

diff --git a/ticdc/ticdc-sink-to-kafka.md b/ticdc/ticdc-sink-to-kafka.md
@@ -241,9 +241,10 @@ This feature splits a single large table into multiple data ranges based on the
 - A single TiCDC node cannot replicate a large single table in time.
 - The resources (such as CPU and memory) consumed by TiCDC nodes are not evenly distributed.
 
-> **Note:**
+> **Warning:**
 >
-> TiCDC v6.6.0 only supports scaling out a large single table on Kafka changefeeds.
+> - Scaling out a single large table is an experimental feature. 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.
+> - TiCDC v6.6.0 only supports scaling out a large single table on Kafka changefeeds.
 
 Sample configuration: