You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@doris.apache.org by mo...@apache.org on 2021/10/10 15:08:28 UTC
[incubator-doris] branch master updated: [Doc] Documentation error
(#6797)
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/incubator-doris.git
The following commit(s) were added to refs/heads/master by this push:
new f439e5e [Doc] Documentation error (#6797)
f439e5e is described below
commit f439e5e533a13d1937407f96209ceebc2504c7d8
Author: jiafeng.zhang <zh...@gmail.com>
AuthorDate: Sun Oct 10 23:08:16 2021 +0800
[Doc] Documentation error (#6797)
Documentation error
---
.../operation/tablet-repair-and-balance.md | 16 ++++++++--------
.../operation/tablet-repair-and-balance.md | 15 ++++++++-------
2 files changed, 16 insertions(+), 15 deletions(-)
diff --git a/docs/en/administrator-guide/operation/tablet-repair-and-balance.md b/docs/en/administrator-guide/operation/tablet-repair-and-balance.md
index 1068dd3..e8173a2 100644
--- a/docs/en/administrator-guide/operation/tablet-repair-and-balance.md
+++ b/docs/en/administrator-guide/operation/tablet-repair-and-balance.md
@@ -298,9 +298,9 @@ Duplicate status view mainly looks at the status of the duplicate, as well as th
2. Table (partition) level status checking
- Users can view the status of a copy of a specified table or partition through the following commands and filter the status through a WHERE statement. If you look at table tbl1, the state on partitions P1 and P2 is a copy of NORMAL:
+ Users can view the status of a copy of a specified table or partition through the following commands and filter the status through a WHERE statement. If you look at table tbl1, the state on partitions P1 and P2 is a copy of OK:
- `ADMIN SHOW REPLICA STATUS FROM tbl1 PARTITION (p1, p2) WHERE STATUS = "NORMAL";`
+ `ADMIN SHOW REPLICA STATUS FROM tbl1 PARTITION (p1, p2) WHERE STATUS = "OK";`
```
+----------+-----------+-----------+---------+-------------------+--------------------+------------------+------------+------------+-------+--------+--------+
@@ -313,7 +313,7 @@ Duplicate status view mainly looks at the status of the duplicate, as well as th
| 29502433 | 44900737 | 10004 | 2 | -1 | -1 | 1 | -1 | 2 | false | NORMAL | OK |
| 29502433 | 48369135 | 10006 | 2 | -1 | -1 | 1 | -1 | 2 | false | NORMAL | OK |
+----------+-----------+-----------+---------+-------------------+--------------------+------------------+------------+------------+-------+--------+--------+
- ```
+ ```
The status of all copies is shown here. Where `IsBad` is listed as `true`, the copy is damaged. The `Status` column displays other states. Specific status description, you can see help through `HELP ADMIN SHOW REPLICA STATUS`.
@@ -329,8 +329,8 @@ Duplicate status view mainly looks at the status of the duplicate, as well as th
| 29502429 | 36885996 | 10002 | 1421156361 | 2 | 0 | -1 | 0 | -1 | 0 | N/A | 784 | 0 | NORMAL | N/A | -1 | -1 | 2 | -1441285706148429853 | url | url |
| 29502429 | 48100551 | 10007 | 1421156361 | 2 | 0 | -1 | 0 | -1 | 0 | N/A | 784 | 0 | NORMAL | N/A | -1 | -1 | 2 | -4784691547051455525 | url | url |
+----------+-----------+-----------+------------+---------+-------------+-------------------+-----------------------+------------------+----------------------+---------------+----------+----------+--------+-------------------------+--------------+----------------------+--------------+----------------------+----------------------+----------------------+
- ```
-
+ ```
+
The figure above shows some additional information, including copy size, number of rows, number of versions, where the data path is located.
> Note: The contents of the `State` column shown here do not represent the health status of the replica, but the status of the replica under certain tasks, such as CLONE, SCHEMA CHANGE, ROLLUP, etc.
@@ -384,7 +384,7 @@ Duplicate status view mainly looks at the status of the duplicate, as well as th
| 39279319 | 10007 | 2 | 0 | -1 | 0 | -1 | 0 | N/A | -1 | 784 | 0 | NORMAL | false | 2 | 1656508631294397870 |
+-----------+-----------+---------+-------------+-------------------+-----------------------+------------------+----------------------+---------------+------------+----------+----------+--------+-------+--------------+----------------------+
```
-
+
The figure above shows all replicas of the corresponding Tablet. The content shown here is the same as `SHOW TABLET FROM tbl1;`. But here you can clearly see the status of all copies of a specific Tablet.
### Duplicate Scheduling Task
@@ -400,7 +400,7 @@ Duplicate status view mainly looks at the status of the duplicate, as well as th
| 4203036 | REPAIR | REPLICA_MISSING | PENDING | HIGH | LOW | -1 | -1 | -1 | -1 | 0 | 2019-02-21 15:00:20 | 2019-02-24 11:18:41 | 2019-02-24 11:18:41 | N/A | N/A | 2 | 0 | 2019-02-21 15:00:43 | 1 | 0 | 2 | 0 | unable to find source replica |
+----------+--------+-----------------+---------+----------+----------+-------+---------+--------+----------+---------+---------------------+---------------------+---------------------+----------+------+-------------+---------------+---------------------+------------+---------------------+--------+---------------------+-------------------------------+
```
-
+
The specific meanings of each column are as follows:
* TabletId: The ID of the Tablet waiting to be scheduled. A scheduling task is for only one Tablet
@@ -500,7 +500,7 @@ Duplicate status view mainly looks at the status of the duplicate, as well as th
| /home/disk2/palo | 881.955 GB | 2.656 TB | 3.525 TB | 24.65 % | ONLINE | 4870995507205544622 |
| /home/disk5/palo | 694.992 GB | 2.842 TB | 3.525 TB | 19.36 % | ONLINE | 1916696897889786739 |
+------------------+------------------+---------------+---------------+---------+--------+----------------------+
- ```
+ ```
The disk usage of each data path on the specified BE is shown here.
diff --git a/docs/zh-CN/administrator-guide/operation/tablet-repair-and-balance.md b/docs/zh-CN/administrator-guide/operation/tablet-repair-and-balance.md
index a6b59f4..44c9204 100644
--- a/docs/zh-CN/administrator-guide/operation/tablet-repair-and-balance.md
+++ b/docs/zh-CN/administrator-guide/operation/tablet-repair-and-balance.md
@@ -76,10 +76,11 @@ under the License.
健康副本。即数据正常的副本,并且副本所在的 BE 节点状态正常(心跳正常且不处于下线过程中)
+
**一个 Tablet 的健康状态由其所有副本的状态决定,有以下几种:**
1. REPLICA\_MISSING
-
+
副本缺失。即存活副本数小于期望副本数。
2. VERSION\_INCOMPLETE
@@ -109,7 +110,7 @@ under the License.
8. COLOCATE\_REDUNDANT
针对 Colocation 属性的表的分片状态。表示 Colocation 表的分片副本冗余。
-
+
9. HEALTHY
健康分片,即条件[1-8]都不满足。
@@ -294,10 +295,10 @@ TabletScheduler 在每轮调度时,都会通过 LoadBalancer 来选择一定
上图会显示具体的不健康的 Tablet ID(40467980)。后面我们会介绍如何查看一个具体的 Tablet 的各个副本的状态。
2. 表(分区)级别状态检查
+
+ 用户可以通过以下命令查看指定表或分区的副本状态,并可以通过 WHERE 语句对状态进行过滤。如查看表 tbl1 中,分区 p1 和 p2 上状态为 OK 的副本:
- 用户可以通过以下命令查看指定表或分区的副本状态,并可以通过 WHERE 语句对状态进行过滤。如查看表 tbl1 中,分区 p1 和 p2 上状态为 NORMAL 的副本:
-
- `ADMIN SHOW REPLICA STATUS FROM tbl1 PARTITION (p1, p2) WHERE STATUS = "NORMAL";`
+ `ADMIN SHOW REPLICA STATUS FROM tbl1 PARTITION (p1, p2) WHERE STATUS = "OK";`
```
+----------+-----------+-----------+---------+-------------------+--------------------+------------------+------------+------------+-------+--------+--------+
@@ -471,7 +472,7 @@ TabletScheduler 在每轮调度时,都会通过 LoadBalancer 来选择一定
| 10000 | default_cluster | true | 4369719923760 | 19377459077121 | 22.551 | 547175 | 0.5 | 0.5 | 1.0964036415787461 | MID |
+----------+-----------------+-----------+---------------+----------------+-------------+------------+----------+-----------+--------------------+-------+
```
-
+
其中一些列的含义如下:
* Available:为 true 表示 BE 心跳正常,且没有处于下线中
@@ -613,7 +614,7 @@ TabletScheduler 在每轮调度时,都会通过 LoadBalancer 来选择一定
* 重要性:高
* schedule\_slot\_num\_per\_path
-
+
* 说明:默认分配给每块磁盘用于副本修复的 slot 数目。该数目表示一块磁盘能同时运行的副本修复任务数。如果想以更快的速度修复副本,可以适当调高这个参数。单数值越高,可能对 IO 影响越大。
* 默认值:2
* 重要性:高
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org
For additional commands, e-mail: commits-help@doris.apache.org