diff --git a/src/UserGuide/Master/Tree/User-Manual/Maintennance.md b/src/UserGuide/Master/Tree/User-Manual/Maintennance.md index 54665e7f4..f25f25181 100644 --- a/src/UserGuide/Master/Tree/User-Manual/Maintennance.md +++ b/src/UserGuide/Master/Tree/User-Manual/Maintennance.md @@ -368,8 +368,7 @@ Here is a schematic diagram of the region migration process : 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 . -4. The region migration process will block the deletion of the WAL file of this consensus group. If the total number of WAL files reaches `wal_file_size_threshold_in_byte `, it will block writing. +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 @@ -416,6 +415,13 @@ Here is a schematic diagram of the region migration process : 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. + ``` + ## Start/Stop Repair Data Statements Used to repair the unsorted data generate by system bug. ### START REPAIR DATA diff --git a/src/UserGuide/latest/User-Manual/Maintennance.md b/src/UserGuide/latest/User-Manual/Maintennance.md index e8c525843..8897eb3f3 100644 --- a/src/UserGuide/latest/User-Manual/Maintennance.md +++ b/src/UserGuide/latest/User-Manual/Maintennance.md @@ -367,9 +367,8 @@ Here is a schematic diagram of the region migration process : ### Notes 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 . -4. The region migration process will block the deletion of the WAL file of this consensus group. If the total number of WAL files reaches `wal_file_size_threshold_in_byte `, it will block writing. +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 @@ -416,6 +415,13 @@ Here is a schematic diagram of the region migration process : 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. + ``` + ## Start/Stop Repair Data Statements Used to repair the unsorted data generate by system bug. ### START REPAIR DATA diff --git a/src/zh/UserGuide/Master/Tree/User-Manual/Maintennance.md b/src/zh/UserGuide/Master/Tree/User-Manual/Maintennance.md index 5598988e1..8dfc70a6d 100644 --- a/src/zh/UserGuide/Master/Tree/User-Manual/Maintennance.md +++ b/src/zh/UserGuide/Master/Tree/User-Manual/Maintennance.md @@ -347,8 +347,7 @@ IoTDB 是一个分布式数据库，数据的均衡分布对集群的磁盘空 1. 仅支持在 IoTDB 1.3.3 以及更高版本使用 region 迁移功能。 2. 目前支持 IoTConsensus、Ratis 协议。见 iotdb-system.properties 中的schema_region_consensus_protocol_class 和 data_region_consensus_protocol_class。 -3. region 迁移需要占用硬盘和网络带宽等系统资源，尽管过程不阻塞读取和写入，但可能影响读写速度。 -4. region 迁移过程会阻塞本共识组 WAL 文件的删除，如果 WAL 文件总量达到`wal_file_size_threshold_in_byte`，则会阻塞写入。 +3. region 迁移需要占用硬盘和网络带宽等系统资源，尽管过程通常不阻塞读取和写入，但可能影响读写速度。阻塞写入情况的具体鉴别与处理方式见使用说明。 ### 使用说明 @@ -404,6 +403,13 @@ 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. + ``` + ## Start/Stop Repair Data 语句 用于修复由于系统 bug 导致的乱序 ### START REPAIR DATA diff --git a/src/zh/UserGuide/latest/User-Manual/Maintennance.md b/src/zh/UserGuide/latest/User-Manual/Maintennance.md index 5598988e1..6a36bc889 100644 --- a/src/zh/UserGuide/latest/User-Manual/Maintennance.md +++ b/src/zh/UserGuide/latest/User-Manual/Maintennance.md @@ -347,8 +347,7 @@ IoTDB 是一个分布式数据库，数据的均衡分布对集群的磁盘空 1. 仅支持在 IoTDB 1.3.3 以及更高版本使用 region 迁移功能。 2. 目前支持 IoTConsensus、Ratis 协议。见 iotdb-system.properties 中的schema_region_consensus_protocol_class 和 data_region_consensus_protocol_class。 -3. region 迁移需要占用硬盘和网络带宽等系统资源，尽管过程不阻塞读取和写入，但可能影响读写速度。 -4. region 迁移过程会阻塞本共识组 WAL 文件的删除，如果 WAL 文件总量达到`wal_file_size_threshold_in_byte`，则会阻塞写入。 +3. region 迁移需要占用硬盘和网络带宽等系统资源，尽管过程通常不阻塞读取和写入，但可能影响读写速度。阻塞写入情况的具体鉴别与处理方式见使用说明。 ### 使用说明 @@ -404,6 +403,13 @@ 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. + ``` + ## Start/Stop Repair Data 语句 用于修复由于系统 bug 导致的乱序 ### START REPAIR DATA