This is an automated email from the ASF dual-hosted git repository.
morningman pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris.git
The following commit(s) were added to refs/heads/master by this push:
new 9ec66f939a [fix](docs) fix the docs of command "show proc
'/statistic'" and ADMIN CHECK TABLET (#14282)
9ec66f939a is described below
commit 9ec66f939a1797d8640b82bfaf0dad7b06fb9ae8
Author: Hong Liu <844981...@qq.com>
AuthorDate: Tue Nov 22 21:53:11 2022 +0800
[fix](docs) fix the docs of command "show proc '/statistic'" and ADMIN
CHECK TABLET (#14282)
Co-authored-by: smallhibiscus <844981280>
---
docs/en/docs/faq/install-faq.md | 4 ++--
.../ADMIN-CHECK-TABLET.md | 25 +++++++++++++---------
docs/zh-CN/docs/faq/install-faq.md | 4 ++--
.../ADMIN-CHECK-TABLET.md | 2 +-
4 files changed, 20 insertions(+), 15 deletions(-)
diff --git a/docs/en/docs/faq/install-faq.md b/docs/en/docs/faq/install-faq.md
index b8f5f88537..a4882740e1 100644
--- a/docs/en/docs/faq/install-faq.md
+++ b/docs/en/docs/faq/install-faq.md
@@ -35,9 +35,9 @@ This document is mainly used to record the common problems of
operation and main
During the offline process, use show backends to view the tabletNum of the
offline node, and you will observe that the number of tabletNum is decreasing,
indicating that data shards are being migrated from this node. When the number
is reduced to 0, the system will automatically delete the node. But in some
cases, tabletNum will not change after it drops to a certain value. This is
usually possible for two reasons:
1. The tablets belong to the table, partition, or materialized view that was
just dropped. Objects that have just been deleted remain in the recycle bin.
The offline logic will not process these shards. The time an object resides in
the recycle bin can be modified by modifying the FE configuration parameter
catalog_trash_expire_second. These tablets are disposed of when the object is
removed from the recycle bin.
-2. There is a problem with the migration task for these tablets. At this
point, you need to view the errors of specific tasks through show proc
"/cluster_balance".
+2. There is a problem with the migration task for these tablets. At this
point, you need to view the errors of specific tasks through show proc `show
proc "/cluster_balance"`.
-For the above situation, you can first check whether there are unhealthy
shards in the cluster through show proc "/statistic". If it is 0, you can
delete the BE directly through the drop backend statement. Otherwise, you also
need to check the replicas of unhealthy shards in detail.
+For the above situation, you can first check whether there are unhealthy
shards in the cluster through `show proc "/cluster_health/tablet_health";`. If
it is 0, you can delete the BE directly through the drop backend statement.
Otherwise, you also need to check the replicas of unhealthy shards in detail.
### Q2. How should priorty_network be set?
diff --git
a/docs/en/docs/sql-manual/sql-reference/Database-Administration-Statements/ADMIN-CHECK-TABLET.md
b/docs/en/docs/sql-manual/sql-reference/Database-Administration-Statements/ADMIN-CHECK-TABLET.md
index 2caf6a144a..cc5a76e340 100644
---
a/docs/en/docs/sql-manual/sql-reference/Database-Administration-Statements/ADMIN-CHECK-TABLET.md
+++
b/docs/en/docs/sql-manual/sql-reference/Database-Administration-Statements/ADMIN-CHECK-TABLET.md
@@ -28,31 +28,35 @@ under the License.
### Name
-ADMIN CLEAN TRASH
+ADMIN CHECK TABLET
### Description
-This statement is used to clean up garbage data in the backend
+This statement is used to perform the specified check operation on a set of
tablets.
grammar:
```sql
-ADMIN CLEAN TRASH [ON ("BackendHost1:BackendHeartBeatPort1",
"BackendHost2:BackendHeartBeatPort2", ...)];
-````
+ADMIN CHECK TABLE (tablet_id1, tablet_id2, ...)
+PROPERTIES("type" = "...");
+```
illustrate:
-1. Use BackendHost:BackendHeartBeatPort to indicate the backend that needs to
be cleaned up, and clean up all backends without adding the on limit.
+1. A list of tablet ids must be specified along with the type property in
PROPERTIES.
+2. Type only supports:
-### Example
+ * consistency: Check the consistency of the replica of the tablet. This
command is an asynchronous command. After sending, Doris will start to execute
the consistency check job of the corresponding tablet. The final result will be
reflected in the InconsistentTabletNum column in the result of `SHOW PROC
"/cluster_health/tablet_health";`.
-1. Clean up the junk data of all be nodes.
- ADMIN CLEAN TRASH;
+### Example
-2. Clean up the junk data of '192.168.0.1:9050' and '192.168.0.2:9050'.
+1. Perform a replica data consistency check on a specified set of tablets.
- ADMIN CLEAN TRASH ON ("192.168.0.1:9050","192.168.0.2:9050");
+ ```
+ ADMIN CHECK TABLET (10000, 10001)
+ PROPERTIES("type" = "consistency");
+ ```
### Keywords
@@ -60,3 +64,4 @@ illustrate:
### Best Practice
+
diff --git a/docs/zh-CN/docs/faq/install-faq.md
b/docs/zh-CN/docs/faq/install-faq.md
index e7c9f6a084..445f4facbb 100644
--- a/docs/zh-CN/docs/faq/install-faq.md
+++ b/docs/zh-CN/docs/faq/install-faq.md
@@ -35,9 +35,9 @@ under the License.
在下线过程中，通过 show backends 查看下线节点的 tabletNum ，会观察到 tabletNum
数量在减少，说明数据分片正在从这个节点迁移走。当数量减到0时，系统会自动删除这个节点。但某些情况下，tabletNum
下降到一定数值后就不变化。这通常可能有以下两种原因：
1. 这些 tablet 属于刚被删除的表、分区或物化视图。而刚被删除的对象会保留在回收站中。而下线逻辑不会处理这些分片。可以通过修改 FE 的配置参数
catalog_trash_expire_second 来修改对象在回收站中驻留的时间。当对象从回收站中被删除后，这些 tablet就会被处理了。
-2. 这些 tablet 的迁移任务出现了问题。此时需要通过 show proc "/cluster_balance" 来查看具体任务的错误了。
+2. 这些 tablet 的迁移任务出现了问题。此时需要通过 `show proc "/cluster_balance"` 来查看具体任务的错误了。
-对于以上情况，可以先通过 show proc "/statistic" 查看集群是否还有 unhealthy 的分片，如果为0，则可以直接通过 drop
backend 语句删除这个 BE 。否则，还需要具体查看不健康分片的副本情况。
+对于以上情况，可以先通过 `show proc "/cluster_health/tablet_health";` 查看集群是否还有 unhealthy
的分片，如果为0，则可以直接通过 drop backend 语句删除这个 BE 。否则，还需要具体查看不健康分片的副本情况。
### Q2. priorty_network 应该如何设置？
diff --git
a/docs/zh-CN/docs/sql-manual/sql-reference/Database-Administration-Statements/ADMIN-CHECK-TABLET.md
b/docs/zh-CN/docs/sql-manual/sql-reference/Database-Administration-Statements/ADMIN-CHECK-TABLET.md
index 879fa9707c..edfa4ed3f0 100644
---
a/docs/zh-CN/docs/sql-manual/sql-reference/Database-Administration-Statements/ADMIN-CHECK-TABLET.md
+++
b/docs/zh-CN/docs/sql-manual/sql-reference/Database-Administration-Statements/ADMIN-CHECK-TABLET.md
@@ -46,7 +46,7 @@ PROPERTIES("type" = "...");
1. 必须指定 tablet id 列表以及 PROPERTIES 中的 type 属性。
2. 目前 type 仅支持：
- * consistency: 对tablet的副本数据一致性进行检查。该命令为异步命令，发送后，Doris 会开始执行对应 tablet
的一致性检查作业。最终的结果，将体现在 `SHOW PROC "/statistic";` 结果中的 InconsistentTabletNum 列。
+ * consistency: 对tablet的副本数据一致性进行检查。该命令为异步命令，发送后，Doris 会开始执行对应 tablet
的一致性检查作业。最终的结果，将体现在 `SHOW PROC "/cluster_health/tablet_health";` 结果中的
InconsistentTabletNum 列。
### Example
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
