This is an automated email from the ASF dual-hosted git repository.

w41ter pushed a commit to branch update_ccr_docs
in repository https://gitbox.apache.org/repos/asf/doris-website.git

commit f0e09eccd9cd75e2327839762aca44023a41329e
Author: w41ter <w41te...@gmail.com>
AuthorDate: Mon Dec 30 02:48:53 2024 +0000

    Add light schema change property requirement
---
 docs/admin-manual/data-admin/ccr/manual.md                 | 14 +++++++++-----
 .../current/admin-manual/data-admin/ccr/manual.md          | 14 +++++++++-----
 2 files changed, 18 insertions(+), 10 deletions(-)

diff --git a/docs/admin-manual/data-admin/ccr/manual.md 
b/docs/admin-manual/data-admin/ccr/manual.md
index a7f9ea5b0ac..1349abe067f 100644
--- a/docs/admin-manual/data-admin/ccr/manual.md
+++ b/docs/admin-manual/data-admin/ccr/manual.md
@@ -57,6 +57,15 @@ Minimum version required: v2.0.15
 Doris Versions:
 - 2.1.5/2.0.14: If upgrading from previous versions to these two versions, and 
the user has a drop partition operation, an NPE may occur during upgrade or 
restart. This is due to a new field introduced in these versions, which older 
versions don't have, causing a default value of null. This issue was fixed in 
2.1.6/2.0.15.
 
+### Configuration and Attribute Requirements
+
+**Attribute Requirements**
+- `light_schema_change`: The Syncer requires both upstream and downstream 
tables to have the `light_schema_table` attribute set, otherwise, data 
synchronization will fail. Note: The latest version of Doris automatically sets 
the `light_schema_change` attribute when creating tables. If using an older 
version of Doris or upgrading from an older version, you need to manually set 
the `light_schema_change` attribute for existing OLAP tables before enabling 
Syncer synchronization.
+
+**Configuration Requirements**
+- `restore_reset_index_id`: If the table to be synchronized has an inverted 
index, this must be set to `false` on the target cluster.
+- `ignore_backup_tmp_partitions`: If temporary partitions are created 
upstream, Doris will prevent backups, causing the Syncer synchronization to 
fail. Setting `ignore_backup_tmp_partitions=true` in FE can avoid this issue.
+
 ## Start Syncer
 
 Start Syncer according to the configurations and save a pid file in the 
default or specified path. The name of the pid file should follow 
`host_port.pid`.
@@ -459,11 +468,6 @@ Under normal circumstances, the `is_being_synced` 
attribute should be entirely c
 
 :::
 
-### Recommended Configuration Settings
-
-- `restore_reset_index_id`: If the table to be synced contains an inverted 
index, this must be set to `false` on the target cluster.
-- `ignore_backup_tmp_partitions`: If the upstream creates temporary 
partitions, Doris will prohibit performing backups, causing the ccr-syncer 
synchronization to break. This can be avoided by setting 
`ignore_backup_tmp_partitions=true` in the FE configuration.
-
 ### Notes
 
 - During CCR synchronization, both backup/restore jobs and binlogs are stored 
in FE memory. Therefore, it is recommended to allocate at least 4GB of heap 
memory per CCR job (for both the source and target clusters). Additionally, 
consider modifying the following configurations to reduce memory consumption 
from unrelated jobs:
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/data-admin/ccr/manual.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/data-admin/ccr/manual.md
index 2ab32e928e2..b3f629cc75e 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/data-admin/ccr/manual.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/data-admin/ccr/manual.md
@@ -57,6 +57,15 @@ Syncer 同步时需要用户提供上下游的账户,该账户需要拥有下
 Doris 版本
 - 2.1.5/2.0.14:如果从之前的版本升级到这两个版本,且用户有 drop partition 操作,那么会在升级、重启时碰到 
NPE,原因是这个版本引入了一个新字段,旧版本没有所以默认值为 null。这个问题在 2.1.6/2.0.15 修复。
 
+### 配置和属性要求
+
+**属性要求**
+- `light_schema_change`:Syncer 要求上下游表都设置 `light_schema_table` 
属性,否则会导致数据同步出错。注意:最新版本的 doris 在建表时会默认设置上 `light_schema_change` 属性,如果是使用老版本的 
doris 或者从老版本升级上来的,需要在开启 Syncer 同步前,给存量 OLAP 表都设置上 `light_schema_change` 属性。
+
+**配置要求**
+- `restore_reset_index_id`:如果要同步的表中带有 inverted index,那么必须在目标集群上配置为 `false`。
+- `ignore_backup_tmp_partitions`:如果上游有创建 tmp partition,那么 doris 会禁止做 backup,因此 
Syncer 同步会中断;通过在 FE 设置 `ignore_backup_tmp_partitions=true` 可以避免这个问题。
+
 ## 启动 Syncer
 
 根据配置选项启动 Syncer,并且在默认或指定路径下保存一个 pid 文件,pid 文件的命名方式为`host_port.pid`。
@@ -472,11 +481,6 @@ CCR 功能在建立同步时,会在目标集群中创建源集群同步范围
 
 :::
 
-### 建议打开的配置
-
-- `restore_reset_index_id`:如果要同步的表中带有 inverted index,那么必须在目标集群上配置为 `false`。
-- `ignore_backup_tmp_partitions`:如果上游有创建 tmp partition,那么 doris 会禁止做 backup,因此 
ccr-syncer 同步会中断;通过在 FE 设置 `ignore_backup_tmp_partitions=true` 可以避免这个问题。
-
 ### 注意事项
 
 - CCR 同步期间 backup/restore job 和 binlogs 都在 FE 内存中,因此建议在 FE 给每个 ccr job 都留出 4GB 
及以上的堆内存(源和目标集群都需要),同时注意修改下列配置减少无关 job 对内存的消耗:


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org

Reply via email to