done

Author: liyuheng55555

src/UserGuide/Master/Tree/User-Manual/Load-Balance.md

@@ -37,10 +37,9 @@ Here is a schematic diagram of the region migration process :
 
 ### Notes
 
-1. It is recommended to only use the Region Migration feature on IoTDB 1.3.3 and higher versions.
-2. Region migration is only supported when the consensus protocol is IoTConsus or Ratis (in iotdb system. properties, the `schema_region_consensus_protocol_class` and`data_region_consensus_protocol_class`).
-3. Region migration will occupy system resources such as hard drives and network bandwidth, and it is recommended to perform it during low business loads.
-4. The region migration process will occupy WAL files, blocking the deletion of WAL files in this consensus group. If the total number of WAL files reaches `wal_file_size_threshold_in_byte`, writing will be blocked.
+1. Region migration is supported only 1.3.3 IoTDB and later.
+2. IoTConsensus and Ratis protocols ( `schema_region_consensus_protocol_class `and `data_region_consensus_protocol_class `in `iotdb-system.properties `) are currently supported .
+3. Region migration requires system resources such as hard disk and internet bandwidth, and although the process does not block reads and writes , it may affect read and write speeds. For detailed identification and handling methods of blocked write scenarios, refer to the following section.
 
 ### Instructions for use
 
@@ -93,3 +92,10 @@ Here is a schematic diagram of the region migration process :
   Total line number = 3
   It costs 0.003s
   ```
+- **Block Write**: Although region migration typically does not block write operations, the cleanup of WAL files needs to be paused during the process. If the accumulation of WAL files reaches the `wal_throttle_threshold_in_byte`, the current DataNode will switch to Readonly mode and suspend writes.
+  If the DataNode enters Readonly mode during migration and sufficient disk space is confirmed, you should increase the `wal_throttle_threshold_in_byte` to 500GB or more to allow writes to continue. Use the following SQL statement:
+  ```plain
+    IoTDB> set configuration "wal_throttle_threshold_in_byte"="536870912000" 
+    Msg: The statement is executed successfully.
+  ```
+  

src/UserGuide/V2.0.1/Tree/User-Manual/Load-Balance.md

@@ -39,8 +39,7 @@ Here is a schematic diagram of the region migration process :
 
 1. It is recommended to only use the Region Migration feature on IoTDB 1.3.3 and higher versions.
 2. Region migration is only supported when the consensus protocol is IoTConsus or Ratis (in iotdb system. properties, the `schema_region_consensus_protocol_class` and`data_region_consensus_protocol_class`).
-3. Region migration will occupy system resources such as hard drives and network bandwidth, and it is recommended to perform it during low business loads.
-4. The region migration process will occupy WAL files, blocking the deletion of WAL files in this consensus group. If the total number of WAL files reaches `wal_file_size_threshold_in_byte`, writing will be blocked.
+3. Region migration requires system resources such as hard disk and internet bandwidth, and although the process does not block reads and writes , it may affect read and write speeds. For detailed identification and handling methods of blocked write scenarios, refer to the following section.
 
 ### Instructions for use
 
@@ -93,3 +92,10 @@ Here is a schematic diagram of the region migration process :
   Total line number = 3
   It costs 0.003s
   ```
+- **Block Write**: Although region migration typically does not block write operations, the cleanup of WAL files needs to be paused during the process. If the accumulation of WAL files reaches the `wal_throttle_threshold_in_byte`, the current DataNode will switch to Readonly mode and suspend writes.
+  If the DataNode enters Readonly mode during migration and sufficient disk space is confirmed, you should increase the `wal_throttle_threshold_in_byte` to 500GB or more to allow writes to continue. Use the following SQL statement:
+  ```plain
+    IoTDB> set configuration "wal_throttle_threshold_in_byte"="536870912000" 
+    Msg: The statement is executed successfully.
+  ```
+  

src/UserGuide/latest/User-Manual/Load-Balance.md

@@ -38,9 +38,8 @@ Here is a schematic diagram of the region migration process :
 ### Notes
 
 1. It is recommended to only use the Region Migration feature on IoTDB 1.3.3 and higher versions.
-2. Region migration is only supported when the consensus protocol is IoTConsus or Ratis (in iotdb system. properties, the `schema_region_consensus_protocol_class` and`data_region_consensus_protocol_class`).
-3. Region migration will occupy system resources such as hard drives and network bandwidth, and it is recommended to perform it during low business loads.
-4. The region migration process will occupy WAL files, blocking the deletion of WAL files in this consensus group. If the total number of WAL files reaches `wal_file_size_threshold_in_byte`, writing will be blocked.
+2. IoTConsensus and Ratis protocols ( `schema_region_consensus_protocol_class `and `data_region_consensus_protocol_class `in `iotdb-system.properties `) are currently supported.
+3. Region migration requires system resources such as hard disk and internet bandwidth, and although the process does not block reads and writes , it may affect read and write speeds. For detailed identification and handling methods of blocked write scenarios, refer to the following section.
 
 ### Instructions for use
 
@@ -93,3 +92,9 @@ Here is a schematic diagram of the region migration process :
   Total line number = 3
   It costs 0.003s
   ```
+- **Block Write**: Although region migration typically does not block write operations, the cleanup of WAL files needs to be paused during the process. If the accumulation of WAL files reaches the `wal_throttle_threshold_in_byte`, the current DataNode will switch to Readonly mode and suspend writes.
+  If the DataNode enters Readonly mode during migration and sufficient disk space is confirmed, you should increase the `wal_throttle_threshold_in_byte` to 500GB or more to allow writes to continue. Use the following SQL statement:
+  ```plain
+    IoTDB> set configuration "wal_throttle_threshold_in_byte"="536870912000" 
+    Msg: The statement is executed successfully.
+  ```

src/zh/UserGuide/Master/Tree/User-Manual/Load-Balance.md

@@ -38,8 +38,7 @@ IoTDB 是一个分布式数据库，数据的均衡分布对集群的磁盘空
 
 1. 推荐仅在 IoTDB 1.3.3 以及更高版本使用 Region 迁移功能。
 2. 仅在共识协议为 IoTConsensus、Ratis 时支持 Region 迁移（iotdb-system.properties中的`schema_region_consensus_protocol_class` 和 `data_region_consensus_protocol_class`）。
-3. Region 迁移会占用硬盘和网络带宽等系统资源，推荐在低业务负载时进行。
-4. Region 迁移过程会占用 WAL 文件，阻塞本共识组 WAL 文件的删除，如果 WAL 文件总量达到`wal_file_size_threshold_in_byte`，则会阻塞写入。
+3. region 迁移需要占用硬盘和网络带宽等系统资源，尽管过程通常不阻塞读取和写入，但可能影响读写速度。阻塞写入情况的具体鉴别与处理方式见使用说明。
 
 ### 使用说明
 
@@ -99,3 +98,10 @@ IoTDB 是一个分布式数据库，数据的均衡分布对集群的磁盘空
   It costs 0.003s
   ```
 
+- **阻塞写入**：尽管 IoTConsensus 的 region 迁移不直接阻塞写入，但由于过程中需要阻塞 WAL 文件的清理，如果 WAL 文件堆积达到`wal_throttle_threshold_in_byte`，那么当前 DataNode 会变为 Readonly 状态，暂停写入。
+  如果迁移过程中 DataNode 变为 Readonly，并且确认有足够的硬盘空间，应将`wal_throttle_threshold_in_byte`调大到 500GB 或更大以允许继续写入。使用 SQL 语句：
+  ```plain
+    IoTDB> set configuration "wal_throttle_threshold_in_byte"="536870912000" 
+    Msg: The statement is executed successfully.
+  ```
+

src/zh/UserGuide/V2.0.1/Tree/User-Manual/Load-Balance.md

@@ -38,8 +38,7 @@ IoTDB 是一个分布式数据库，数据的均衡分布对集群的磁盘空
 
 1. 推荐仅在 IoTDB 1.3.3 以及更高版本使用 Region 迁移功能。
 2. 仅在共识协议为 IoTConsensus、Ratis 时支持 Region 迁移（iotdb-system.properties中的`schema_region_consensus_protocol_class` 和 `data_region_consensus_protocol_class`）。
-3. Region 迁移会占用硬盘和网络带宽等系统资源，推荐在低业务负载时进行。
-4. Region 迁移过程会占用 WAL 文件，阻塞本共识组 WAL 文件的删除，如果 WAL 文件总量达到`wal_file_size_threshold_in_byte`，则会阻塞写入。
+3. region 迁移需要占用硬盘和网络带宽等系统资源，尽管过程通常不阻塞读取和写入，但可能影响读写速度。阻塞写入情况的具体鉴别与处理方式见使用说明。
 
 ### 使用说明
 
@@ -99,3 +98,9 @@ IoTDB 是一个分布式数据库，数据的均衡分布对集群的磁盘空
   It costs 0.003s
   ```
 
+- **阻塞写入**：尽管 IoTConsensus 的 region 迁移不直接阻塞写入，但由于过程中需要阻塞 WAL 文件的清理，如果 WAL 文件堆积达到`wal_throttle_threshold_in_byte`，那么当前 DataNode 会变为 Readonly 状态，暂停写入。
+  如果迁移过程中 DataNode 变为 Readonly，并且确认有足够的硬盘空间，应将`wal_throttle_threshold_in_byte`调大到 500GB 或更大以允许继续写入。使用 SQL 语句：
+  ```plain
+    IoTDB> set configuration "wal_throttle_threshold_in_byte"="536870912000" 
+    Msg: The statement is executed successfully.
+  ```

src/zh/UserGuide/latest/User-Manual/Load-Balance.md

@@ -38,8 +38,7 @@ IoTDB 是一个分布式数据库，数据的均衡分布对集群的磁盘空
 
 1. 推荐仅在 IoTDB 1.3.3 以及更高版本使用 Region 迁移功能。
 2. 仅在共识协议为 IoTConsensus、Ratis 时支持 Region 迁移（iotdb-system.properties中的`schema_region_consensus_protocol_class` 和 `data_region_consensus_protocol_class`）。
-3. Region 迁移会占用硬盘和网络带宽等系统资源，推荐在低业务负载时进行。
-4. Region 迁移过程会占用 WAL 文件，阻塞本共识组 WAL 文件的删除，如果 WAL 文件总量达到`wal_file_size_threshold_in_byte`，则会阻塞写入。
+3. region 迁移需要占用硬盘和网络带宽等系统资源，尽管过程通常不阻塞读取和写入，但可能影响读写速度。阻塞写入情况的具体鉴别与处理方式见使用说明。
 
 ### 使用说明
 
@@ -99,3 +98,10 @@ IoTDB 是一个分布式数据库，数据的均衡分布对集群的磁盘空
   It costs 0.003s
   ```
 
+- **阻塞写入**：尽管 IoTConsensus 的 region 迁移不直接阻塞写入，但由于过程中需要阻塞 WAL 文件的清理，如果 WAL 文件堆积达到`wal_throttle_threshold_in_byte`，那么当前 DataNode 会变为 Readonly 状态，暂停写入。
+  如果迁移过程中 DataNode 变为 Readonly，并且确认有足够的硬盘空间，应将`wal_throttle_threshold_in_byte`调大到 500GB 或更大以允许继续写入。使用 SQL 语句：
+  ```plain
+    IoTDB> set configuration "wal_throttle_threshold_in_byte"="536870912000" 
+    Msg: The statement is executed successfully.
+  ```
+