This is an automated email from the ASF dual-hosted git repository.
qiaojialin pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/iotdb-docs.git
The following commit(s) were added to refs/heads/main by this push:
new 50e0b60e Repair data docs (#195)
50e0b60e is described below
commit 50e0b60eafce5121ceb6055008e91349b57272d8
Author: shuwenwei <[email protected]>
AuthorDate: Fri Nov 8 16:53:18 2024 +0800
Repair data docs (#195)
---
.../Security-Management_apache.md | 12 ++++++++++
.../Security-Management_timecho.md | 12 ++++++++++
.../Master/Reference/Common-Config-Manual.md | 9 ++++++++
src/UserGuide/Master/SQL-Manual/SQL-Manual.md | 12 ++++++++++
src/UserGuide/Master/User-Manual/Maintennance.md | 23 +++++++++++++++++++
.../Administration-Management/Administration.md | 12 ++++++++++
.../stage/Maintenance-Tools/Maintenance-Command.md | 21 +++++++++++++++++
.../Security-Management_apache.md | 12 ++++++++++
.../Security-Management_timecho.md | 12 ++++++++++
.../latest/Reference/Common-Config-Manual.md | 9 ++++++++
src/UserGuide/latest/SQL-Manual/SQL-Manual.md | 12 ++++++++++
src/UserGuide/latest/User-Manual/Maintennance.md | 26 +++++++++++++++++++++-
.../Administration-Management/Administration.md | 12 ++++++++++
.../stage/Maintenance-Tools/Maintenance-Command.md | 21 +++++++++++++++++
.../Master/Reference/Common-Config-Manual.md | 9 ++++++++
.../UserGuide/Master/User-Manual/Maintennance.md | 25 ++++++++++++++++++++-
.../Administration-Management/Administration.md | 12 ++++++++++
.../stage/Maintenance-Tools/Maintenance-Command.md | 19 ++++++++++++++++
.../latest/Reference/Common-Config-Manual.md | 9 ++++++++
.../UserGuide/latest/User-Manual/Maintennance.md | 25 ++++++++++++++++++++-
.../Administration-Management/Administration.md | 12 ++++++++++
.../stage/Maintenance-Tools/Maintenance-Command.md | 19 ++++++++++++++++
22 files changed, 332 insertions(+), 3 deletions(-)
diff --git
a/src/UserGuide/Master/Deployment-and-Maintenance/Security-Management_apache.md
b/src/UserGuide/Master/Deployment-and-Maintenance/Security-Management_apache.md
index 7c873b68..e8e4e897 100644
---
a/src/UserGuide/Master/Deployment-and-Maintenance/Security-Management_apache.md
+++
b/src/UserGuide/Master/Deployment-and-Maintenance/Security-Management_apache.md
@@ -497,6 +497,18 @@ Eg: IoTDB > FULL MERGE
Eg: IoTDB > CLEAR CACHE
```
+- START REPAIR DATA
+
+```sql
+Eg: IoTDB > START REPAIR DATA
+```
+
+- STOP REPAIR DATA
+
+```sql
+Eg: IoTDB > STOP REPAIR DATA
+```
+
- SET SYSTEM TO READONLY / WRITABLE
```
diff --git
a/src/UserGuide/Master/Deployment-and-Maintenance/Security-Management_timecho.md
b/src/UserGuide/Master/Deployment-and-Maintenance/Security-Management_timecho.md
index 13e25b04..94b755e9 100644
---
a/src/UserGuide/Master/Deployment-and-Maintenance/Security-Management_timecho.md
+++
b/src/UserGuide/Master/Deployment-and-Maintenance/Security-Management_timecho.md
@@ -505,6 +505,18 @@ Eg: IoTDB > FULL MERGE
Eg: IoTDB > CLEAR CACHE
```
+- START REPAIR DATA
+
+```sql
+Eg: IoTDB > START REPAIR DATA
+```
+
+- STOP REPAIR DATA
+
+```sql
+Eg: IoTDB > STOP REPAIR DATA
+```
+
- SET SYSTEM TO READONLY / WRITABLE
```
diff --git a/src/UserGuide/Master/Reference/Common-Config-Manual.md
b/src/UserGuide/Master/Reference/Common-Config-Manual.md
index 6eb96364..75625722 100644
--- a/src/UserGuide/Master/Reference/Common-Config-Manual.md
+++ b/src/UserGuide/Master/Reference/Common-Config-Manual.md
@@ -1129,6 +1129,15 @@ Different configuration parameters take effect in the
following three ways:
|Default| 50 |
|Effective| After restart system |
+* compaction\_schedule\_thread\_num
+
+|Name| compaction\_schedule\_thread\_num
|
+|:---:|:--------------------------------------------------------------------------|
+|Description| The number of threads to be set up to select compaction task. |
+|Type| Int32
|
+|Default| 4
|
+|Effective| hot-load
|
+
### Write Ahead Log Configuration
* wal\_mode
diff --git a/src/UserGuide/Master/SQL-Manual/SQL-Manual.md
b/src/UserGuide/Master/SQL-Manual/SQL-Manual.md
index d7d576d4..f66a4b94 100644
--- a/src/UserGuide/Master/SQL-Manual/SQL-Manual.md
+++ b/src/UserGuide/Master/SQL-Manual/SQL-Manual.md
@@ -1735,6 +1735,18 @@ Eg: IoTDB > FULL MERGE
Eg: IoTDB > CLEAR CACHE
```
+- START REPAIR DATA
+
+```sql
+Eg: IoTDB > START REPAIR DATA
+```
+
+- STOP REPAIR DATA
+
+```sql
+Eg: IoTDB > STOP REPAIR DATA
+```
+
- SET SYSTEM TO READONLY / WRITABLE
```
diff --git a/src/UserGuide/Master/User-Manual/Maintennance.md
b/src/UserGuide/Master/User-Manual/Maintennance.md
index 8011151b..4f2e88b1 100644
--- a/src/UserGuide/Master/User-Manual/Maintennance.md
+++ b/src/UserGuide/Master/User-Manual/Maintennance.md
@@ -347,3 +347,26 @@ Observing the results, we found that it is because the
query did not add a time
The final optimization plan is: Add a time filtering condition to avoid a full
table scan.
+## Start/Stop Repair Data Statements
+Used to repair the unsorted data generate by system bug.
+### START REPAIR DATA
+
+Start a repair task to scan all files created before current time.
+The repair task will scan all tsfiles and repair some bad files.
+
+```sql
+IoTDB> START REPAIR DATA
+IoTDB> START REPAIR DATA ON LOCAL
+IoTDB> START REPAIR DATA ON CLUSTER
+```
+
+### STOP REPAIR DATA
+
+Stop the running repair task. To restart the stopped task.
+If there is a stopped repair task, it can be restart and recover the repair
progress by executing SQL `START REPAIR DATA`.
+
+```sql
+IoTDB> STOP REPAIR DATA
+IoTDB> STOP REPAIR DATA ON LOCAL
+IoTDB> STOP REPAIR DATA ON CLUSTER
+```
diff --git
a/src/UserGuide/Master/stage/Administration-Management/Administration.md
b/src/UserGuide/Master/stage/Administration-Management/Administration.md
index a5a39df5..44219a5e 100644
--- a/src/UserGuide/Master/stage/Administration-Management/Administration.md
+++ b/src/UserGuide/Master/stage/Administration-Management/Administration.md
@@ -501,6 +501,18 @@ Eg: IoTDB > FULL MERGE
Eg: IoTDB > CLEAR CACHE
```
+- START REPAIR DATA
+
+```sql
+Eg: IoTDB > START REPAIR DATA
+```
+
+- STOP REPAIR DATA
+
+```sql
+Eg: IoTDB > STOP REPAIR DATA
+```
+
- SET SYSTEM TO READONLY / WRITABLE
```
diff --git
a/src/UserGuide/Master/stage/Maintenance-Tools/Maintenance-Command.md
b/src/UserGuide/Master/stage/Maintenance-Tools/Maintenance-Command.md
index c981788b..9d9ced83 100644
--- a/src/UserGuide/Master/stage/Maintenance-Tools/Maintenance-Command.md
+++ b/src/UserGuide/Master/stage/Maintenance-Tools/Maintenance-Command.md
@@ -47,6 +47,27 @@ IoTDB> CLEAR CACHE ON LOCAL
IoTDB> CLEAR CACHE ON CLUSTER
```
+## START REPAIR DATA
+
+Start a repair task to scan all files created before current time.
+The repair task will scan all tsfiles and repair some bad files.
+
+```sql
+IoTDB> START REPAIR DATA
+IoTDB> START REPAIR DATA ON LOCAL
+IoTDB> START REPAIR DATA ON CLUSTER
+```
+
+## STOP REPAIR DATA
+
+Stop the running repair task. To restart the stopped task.
+If there is a stopped repair task, it can be restart and recover the repair
progress by executing SQL `START REPAIR DATA`.
+
+```sql
+IoTDB> STOP REPAIR DATA
+IoTDB> STOP REPAIR DATA ON LOCAL
+IoTDB> STOP REPAIR DATA ON CLUSTER
+```
## SET SYSTEM TO READONLY / RUNNING
diff --git
a/src/UserGuide/latest/Deployment-and-Maintenance/Security-Management_apache.md
b/src/UserGuide/latest/Deployment-and-Maintenance/Security-Management_apache.md
index 7c873b68..e8e4e897 100644
---
a/src/UserGuide/latest/Deployment-and-Maintenance/Security-Management_apache.md
+++
b/src/UserGuide/latest/Deployment-and-Maintenance/Security-Management_apache.md
@@ -497,6 +497,18 @@ Eg: IoTDB > FULL MERGE
Eg: IoTDB > CLEAR CACHE
```
+- START REPAIR DATA
+
+```sql
+Eg: IoTDB > START REPAIR DATA
+```
+
+- STOP REPAIR DATA
+
+```sql
+Eg: IoTDB > STOP REPAIR DATA
+```
+
- SET SYSTEM TO READONLY / WRITABLE
```
diff --git
a/src/UserGuide/latest/Deployment-and-Maintenance/Security-Management_timecho.md
b/src/UserGuide/latest/Deployment-and-Maintenance/Security-Management_timecho.md
index 13e25b04..94b755e9 100644
---
a/src/UserGuide/latest/Deployment-and-Maintenance/Security-Management_timecho.md
+++
b/src/UserGuide/latest/Deployment-and-Maintenance/Security-Management_timecho.md
@@ -505,6 +505,18 @@ Eg: IoTDB > FULL MERGE
Eg: IoTDB > CLEAR CACHE
```
+- START REPAIR DATA
+
+```sql
+Eg: IoTDB > START REPAIR DATA
+```
+
+- STOP REPAIR DATA
+
+```sql
+Eg: IoTDB > STOP REPAIR DATA
+```
+
- SET SYSTEM TO READONLY / WRITABLE
```
diff --git a/src/UserGuide/latest/Reference/Common-Config-Manual.md
b/src/UserGuide/latest/Reference/Common-Config-Manual.md
index 3eb1100d..a9d702ee 100644
--- a/src/UserGuide/latest/Reference/Common-Config-Manual.md
+++ b/src/UserGuide/latest/Reference/Common-Config-Manual.md
@@ -1036,6 +1036,15 @@ Different configuration parameters take effect in the
following three ways:
|Default| 50 |
|Effective| After restart system |
+* compaction\_schedule\_thread\_num
+
+|Name| compaction\_schedule\_thread\_num
|
+|:---:|:--------------------------------------------------------------------------|
+|Description| The number of threads to be set up to select compaction task. |
+|Type| Int32
|
+|Default| 4
|
+|Effective| hot-load
|
+
### Write Ahead Log Configuration
* wal\_mode
diff --git a/src/UserGuide/latest/SQL-Manual/SQL-Manual.md
b/src/UserGuide/latest/SQL-Manual/SQL-Manual.md
index a943ff24..714ac898 100644
--- a/src/UserGuide/latest/SQL-Manual/SQL-Manual.md
+++ b/src/UserGuide/latest/SQL-Manual/SQL-Manual.md
@@ -1733,6 +1733,18 @@ Eg: IoTDB > FULL MERGE
Eg: IoTDB > CLEAR CACHE
```
+- START REPAIR DATA
+
+```sql
+Eg: IoTDB > START REPAIR DATA
+```
+
+- STOP REPAIR DATA
+
+```sql
+Eg: IoTDB > STOP REPAIR DATA
+```
+
- SET SYSTEM TO READONLY / WRITABLE
```
diff --git a/src/UserGuide/latest/User-Manual/Maintennance.md
b/src/UserGuide/latest/User-Manual/Maintennance.md
index cae05a50..4d75ed6a 100644
--- a/src/UserGuide/latest/User-Manual/Maintennance.md
+++ b/src/UserGuide/latest/User-Manual/Maintennance.md
@@ -344,4 +344,28 @@ When executing explain analyze verbose, even if the query
times out, the interme
Observing the results, we found that it is because the query did not add a
time condition, involving too much data, and the time of
constructAlignedChunkReadersDiskTime and pageReadersDecodeAlignedDiskTime has
been increasing, which means that new chunks are being read all the time.
However, the output information of AlignedSeriesScanNode has always been 0,
because the operator only gives up the time slice and updates the information
when at least one line of data that meets the conditio [...]
-The final optimization plan is: Add a time filtering condition to avoid a full
table scan.
\ No newline at end of file
+The final optimization plan is: Add a time filtering condition to avoid a full
table scan.
+
+## Start/Stop Repair Data Statements
+Used to repair the unsorted data generate by system bug.(Supported version:
1.3.1 and later)
+### START REPAIR DATA
+
+Start a repair task to scan all files created before current time.
+The repair task will scan all tsfiles and repair some bad files.
+
+```sql
+IoTDB> START REPAIR DATA
+IoTDB> START REPAIR DATA ON LOCAL
+IoTDB> START REPAIR DATA ON CLUSTER
+```
+
+### STOP REPAIR DATA
+
+Stop the running repair task. To restart the stopped task.
+If there is a stopped repair task, it can be restart and recover the repair
progress by executing SQL `START REPAIR DATA`.
+
+```sql
+IoTDB> STOP REPAIR DATA
+IoTDB> STOP REPAIR DATA ON LOCAL
+IoTDB> STOP REPAIR DATA ON CLUSTER
+```
diff --git
a/src/UserGuide/latest/stage/Administration-Management/Administration.md
b/src/UserGuide/latest/stage/Administration-Management/Administration.md
index a5a39df5..44219a5e 100644
--- a/src/UserGuide/latest/stage/Administration-Management/Administration.md
+++ b/src/UserGuide/latest/stage/Administration-Management/Administration.md
@@ -501,6 +501,18 @@ Eg: IoTDB > FULL MERGE
Eg: IoTDB > CLEAR CACHE
```
+- START REPAIR DATA
+
+```sql
+Eg: IoTDB > START REPAIR DATA
+```
+
+- STOP REPAIR DATA
+
+```sql
+Eg: IoTDB > STOP REPAIR DATA
+```
+
- SET SYSTEM TO READONLY / WRITABLE
```
diff --git
a/src/UserGuide/latest/stage/Maintenance-Tools/Maintenance-Command.md
b/src/UserGuide/latest/stage/Maintenance-Tools/Maintenance-Command.md
index c981788b..7070ae53 100644
--- a/src/UserGuide/latest/stage/Maintenance-Tools/Maintenance-Command.md
+++ b/src/UserGuide/latest/stage/Maintenance-Tools/Maintenance-Command.md
@@ -47,6 +47,27 @@ IoTDB> CLEAR CACHE ON LOCAL
IoTDB> CLEAR CACHE ON CLUSTER
```
+## START REPAIR DATA
+
+Start a repair task to scan all files created before current time.
+The repair task will scan all tsfiles and repair some bad files.(Supported
version: 1.3.1 and later)
+
+```sql
+IoTDB> START REPAIR DATA
+IoTDB> START REPAIR DATA ON LOCAL
+IoTDB> START REPAIR DATA ON CLUSTER
+```
+
+## STOP REPAIR DATA
+
+Stop the running repair task. To restart the stopped task.
+If there is a stopped repair task, it can be restart and recover the repair
progress by executing SQL `START REPAIR DATA`.(Supported version: 1.3.1 and
later)
+
+```sql
+IoTDB> STOP REPAIR DATA
+IoTDB> STOP REPAIR DATA ON LOCAL
+IoTDB> STOP REPAIR DATA ON CLUSTER
+```
## SET SYSTEM TO READONLY / RUNNING
diff --git a/src/zh/UserGuide/Master/Reference/Common-Config-Manual.md
b/src/zh/UserGuide/Master/Reference/Common-Config-Manual.md
index eee800cd..f709c975 100644
--- a/src/zh/UserGuide/Master/Reference/Common-Config-Manual.md
+++ b/src/zh/UserGuide/Master/Reference/Common-Config-Manual.md
@@ -1146,6 +1146,15 @@ IoTDB ConfigNode 和 DataNode 的公共配置参数位于 `conf` 目录下。
|默认值| 50 |
|改后生效方式| 重启生效 |
+* compaction\_schedule\_thread\_num
+
+|名字| compaction\_schedule\_thread\_num |
+|:---:|:-----------------------------------------|
+|描述| 选择合并任务的线程数量 |
+|类型| int32 |
+|默认值| 4 |
+|改后生效方式| 热加载 |
+
#### 写前日志配置
* wal\_mode
diff --git a/src/zh/UserGuide/Master/User-Manual/Maintennance.md
b/src/zh/UserGuide/Master/User-Manual/Maintennance.md
index 57ab49af..b1cb1941 100644
--- a/src/zh/UserGuide/Master/User-Manual/Maintennance.md
+++ b/src/zh/UserGuide/Master/User-Manual/Maintennance.md
@@ -325,4 +325,27 @@ select count(s1) as total from root.db.d1 where s1 like
'%XXXXXXXX%'
观察结果，我们发现是因为查询未加时间条件，涉及的数据太多 constructAlignedChunkReadersDiskTime 和
pageReadersDecodeAlignedDiskTime的耗时一直在涨，意味着一直在读新的 chunk。但 AlignedSeriesScanNode
的输出信息一直是
0，这是因为算子只有在输出至少一行满足条件的数据时，才会让出时间片，并更新信息。从总的读取耗时（loadTimeSeriesMetadataAlignedDiskSeqTime
+ loadTimeSeriesMetadataAlignedDiskUnSeqTime +
constructAlignedChunkReadersDiskTime +
pageReadersDecodeAlignedDiskTime=约13.4秒）来看，其他耗时（60s - 13.4 =
46.6）应该都是在执行过滤条件上（like 谓词的执行很耗时）。
-最终优化方案为：增加时间过滤条件，避免全表扫描
\ No newline at end of file
+最终优化方案为：增加时间过滤条件，避免全表扫描
+
+## Start/Stop Repair Data 语句
+用于修复由于系统 bug 导致的乱序
+### START REPAIR DATA
+
+启动一个数据修复任务，扫描创建修复任务的时间之前产生的 tsfile 文件并修复有乱序错误的文件。
+
+```sql
+IoTDB> START REPAIR DATA
+IoTDB> START REPAIR DATA ON LOCAL
+IoTDB> START REPAIR DATA ON CLUSTER
+```
+
+### STOP REPAIR DATA
+
+停止一个进行中的修复任务。如果需要再次恢复一个已停止的数据修复任务的进度，可以重新执行 `START REPAIR DATA`.
+
+```sql
+IoTDB> STOP REPAIR DATA
+IoTDB> STOP REPAIR DATA ON LOCAL
+IoTDB> STOP REPAIR DATA ON CLUSTER
+```
+
diff --git
a/src/zh/UserGuide/Master/stage/Administration-Management/Administration.md
b/src/zh/UserGuide/Master/stage/Administration-Management/Administration.md
index 797f2a9e..babb7793 100644
--- a/src/zh/UserGuide/Master/stage/Administration-Management/Administration.md
+++ b/src/zh/UserGuide/Master/stage/Administration-Management/Administration.md
@@ -497,6 +497,18 @@ Eg: IoTDB > FULL MERGE
Eg: IoTDB > CLEAR CACHE
```
+- START REPAIR DATA
+
+```sql
+Eg: IoTDB > START REPAIR DATA
+```
+
+- STOP REPAIR DATA
+
+```sql
+Eg: IoTDB > STOP REPAIR DATA
+```
+
- SET SYSTEM TO READONLY / WRITABLE
```
diff --git
a/src/zh/UserGuide/Master/stage/Maintenance-Tools/Maintenance-Command.md
b/src/zh/UserGuide/Master/stage/Maintenance-Tools/Maintenance-Command.md
index f56c9072..10b99406 100644
--- a/src/zh/UserGuide/Master/stage/Maintenance-Tools/Maintenance-Command.md
+++ b/src/zh/UserGuide/Master/stage/Maintenance-Tools/Maintenance-Command.md
@@ -47,6 +47,25 @@ IoTDB> CLEAR CACHE ON LOCAL
IoTDB> CLEAR CACHE ON CLUSTER
```
+## START REPAIR DATA
+
+启动一个数据修复任务，扫描创建修复任务的时间之前产生的 tsfile 文件并修复有乱序错误的文件。
+
+```sql
+IoTDB> START REPAIR DATA
+IoTDB> START REPAIR DATA ON LOCAL
+IoTDB> START REPAIR DATA ON CLUSTER
+```
+
+## STOP REPAIR DATA
+
+停止一个进行中的修复任务。如果需要再次恢复一个已停止的数据修复任务的进度，可以重新执行 `START REPAIR DATA`.
+
+```sql
+IoTDB> STOP REPAIR DATA
+IoTDB> STOP REPAIR DATA ON LOCAL
+IoTDB> STOP REPAIR DATA ON CLUSTER
+```
## SET SYSTEM TO READONLY / RUNNING
diff --git a/src/zh/UserGuide/latest/Reference/Common-Config-Manual.md
b/src/zh/UserGuide/latest/Reference/Common-Config-Manual.md
index 4a84bce8..575be023 100644
--- a/src/zh/UserGuide/latest/Reference/Common-Config-Manual.md
+++ b/src/zh/UserGuide/latest/Reference/Common-Config-Manual.md
@@ -1079,6 +1079,15 @@ IoTDB ConfigNode 和 DataNode 的公共配置参数位于 `conf` 目录下。
|默认值| 50 |
|改后生效方式| 重启生效 |
+* compaction\_schedule\_thread\_num
+
+|名字| compaction\_schedule\_thread\_num |
+|:---:|:-----------------------------------------|
+|描述| 选择合并任务的线程数量 |
+|类型| int32 |
+|默认值| 4 |
+|改后生效方式| 热加载 |
+
#### 写前日志配置
* wal\_mode
diff --git a/src/zh/UserGuide/latest/User-Manual/Maintennance.md
b/src/zh/UserGuide/latest/User-Manual/Maintennance.md
index eb39c061..f0bc0584 100644
--- a/src/zh/UserGuide/latest/User-Manual/Maintennance.md
+++ b/src/zh/UserGuide/latest/User-Manual/Maintennance.md
@@ -325,4 +325,27 @@ select count(s1) as total from root.db.d1 where s1 like
'%XXXXXXXX%'
观察结果，我们发现是因为查询未加时间条件，涉及的数据太多 constructAlignedChunkReadersDiskTime 和
pageReadersDecodeAlignedDiskTime的耗时一直在涨，意味着一直在读新的 chunk。但 AlignedSeriesScanNode
的输出信息一直是
0，这是因为算子只有在输出至少一行满足条件的数据时，才会让出时间片，并更新信息。从总的读取耗时（loadTimeSeriesMetadataAlignedDiskSeqTime
+ loadTimeSeriesMetadataAlignedDiskUnSeqTime +
constructAlignedChunkReadersDiskTime +
pageReadersDecodeAlignedDiskTime=约13.4秒）来看，其他耗时（60s - 13.4 =
46.6）应该都是在执行过滤条件上（like 谓词的执行很耗时）。
-最终优化方案为：增加时间过滤条件，避免全表扫描
\ No newline at end of file
+最终优化方案为：增加时间过滤条件，避免全表扫描
+
+## Start/Stop Repair Data 语句
+用于修复由于系统 bug 导致的乱序（1.3.1 以上版本支持此命令）
+### START REPAIR DATA
+
+启动一个数据修复任务，扫描创建修复任务的时间之前产生的 tsfile 文件并修复有乱序错误的文件。
+
+```sql
+IoTDB> START REPAIR DATA
+IoTDB> START REPAIR DATA ON LOCAL
+IoTDB> START REPAIR DATA ON CLUSTER
+```
+
+### STOP REPAIR DATA
+
+停止一个进行中的修复任务。如果需要再次恢复一个已停止的数据修复任务的进度，可以重新执行 `START REPAIR DATA`.
+
+```sql
+IoTDB> STOP REPAIR DATA
+IoTDB> STOP REPAIR DATA ON LOCAL
+IoTDB> STOP REPAIR DATA ON CLUSTER
+```
+
diff --git
a/src/zh/UserGuide/latest/stage/Administration-Management/Administration.md
b/src/zh/UserGuide/latest/stage/Administration-Management/Administration.md
index 797f2a9e..babb7793 100644
--- a/src/zh/UserGuide/latest/stage/Administration-Management/Administration.md
+++ b/src/zh/UserGuide/latest/stage/Administration-Management/Administration.md
@@ -497,6 +497,18 @@ Eg: IoTDB > FULL MERGE
Eg: IoTDB > CLEAR CACHE
```
+- START REPAIR DATA
+
+```sql
+Eg: IoTDB > START REPAIR DATA
+```
+
+- STOP REPAIR DATA
+
+```sql
+Eg: IoTDB > STOP REPAIR DATA
+```
+
- SET SYSTEM TO READONLY / WRITABLE
```
diff --git
a/src/zh/UserGuide/latest/stage/Maintenance-Tools/Maintenance-Command.md
b/src/zh/UserGuide/latest/stage/Maintenance-Tools/Maintenance-Command.md
index f56c9072..983e5799 100644
--- a/src/zh/UserGuide/latest/stage/Maintenance-Tools/Maintenance-Command.md
+++ b/src/zh/UserGuide/latest/stage/Maintenance-Tools/Maintenance-Command.md
@@ -47,6 +47,25 @@ IoTDB> CLEAR CACHE ON LOCAL
IoTDB> CLEAR CACHE ON CLUSTER
```
+## START REPAIR DATA
+
+启动一个数据修复任务，扫描创建修复任务的时间之前产生的 tsfile 文件并修复有乱序错误的文件。(支持版本：1.3.1以上)
+
+```sql
+IoTDB> START REPAIR DATA
+IoTDB> START REPAIR DATA ON LOCAL
+IoTDB> START REPAIR DATA ON CLUSTER
+```
+
+## STOP REPAIR DATA
+
+停止一个进行中的修复任务。如果需要再次恢复一个已停止的数据修复任务的进度，可以重新执行 `START REPAIR DATA`。(支持版本：1.3.1以上)
+
+```sql
+IoTDB> STOP REPAIR DATA
+IoTDB> STOP REPAIR DATA ON LOCAL
+IoTDB> STOP REPAIR DATA ON CLUSTER
+```
## SET SYSTEM TO READONLY / RUNNING
