This is an automated email from the ASF dual-hosted git repository.
yiguolei 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 39dd6682f2 [typo](docs)change the metadata directory from palo-meta to
doris-meta #14647
39dd6682f2 is described below
commit 39dd6682f25d6948afc2260d883e313216e3a373
Author: zy-kkk <zhong...@qq.com>
AuthorDate: Tue Nov 29 08:52:55 2022 +0800
[typo](docs)change the metadata directory from palo-meta to doris-meta
#14647
---
.../en/community/developer-guide/fe-eclipse-dev.md | 2 +-
.../http-actions/fe/bootstrap-action.md | 4 ++--
.../admin-manual/http-actions/fe/get-small-file.md | 2 +-
.../maint-monitor/metadata-operation.md | 24 +++++++++++-----------
.../community/developer-guide/fe-eclipse-dev.md | 2 +-
.../http-actions/fe/bootstrap-action.md | 4 ++--
.../admin-manual/http-actions/fe/get-small-file.md | 2 +-
.../maint-monitor/metadata-operation.md | 24 +++++++++++-----------
8 files changed, 32 insertions(+), 32 deletions(-)
diff --git a/docs/en/community/developer-guide/fe-eclipse-dev.md
b/docs/en/community/developer-guide/fe-eclipse-dev.md
index dbbb130a80..890f89f091 100644
--- a/docs/en/community/developer-guide/fe-eclipse-dev.md
+++ b/docs/en/community/developer-guide/fe-eclipse-dev.md
@@ -158,7 +158,7 @@ You can directly start an FE process in Eclipse to
facilitate debugging the code
```
mkdir /path/to/doris/fe/run/
cd /path/to/doris/fe/run/
- mkdir conf/ log/ palo-meta/
+ mkdir conf/log/doris-meta/
```
2. Create configuration file
diff --git a/docs/en/docs/admin-manual/http-actions/fe/bootstrap-action.md
b/docs/en/docs/admin-manual/http-actions/fe/bootstrap-action.md
index 1f30ca3498..d08b932dd2 100644
--- a/docs/en/docs/admin-manual/http-actions/fe/bootstrap-action.md
+++ b/docs/en/docs/admin-manual/http-actions/fe/bootstrap-action.md
@@ -42,11 +42,11 @@ none
* `cluster_id`
- The cluster id. It can be viewed in the file `palo-meta/image/VERSION`.
+ The cluster id. It can be viewed in the file `doris-meta/image/VERSION`.
* `token`
- Cluster token. It can be viewed in the file `palo-meta/image/VERSION`.
+ Cluster token. It can be viewed in the file `doris-meta/image/VERSION`.
## Request body
diff --git a/docs/en/docs/admin-manual/http-actions/fe/get-small-file.md
b/docs/en/docs/admin-manual/http-actions/fe/get-small-file.md
index bd65a01b85..4a22a7c00b 100644
--- a/docs/en/docs/admin-manual/http-actions/fe/get-small-file.md
+++ b/docs/en/docs/admin-manual/http-actions/fe/get-small-file.md
@@ -42,7 +42,7 @@ None
* `token`
- The token of the cluster. It can be viewed in the file
`palo-meta/image/VERSION`.
+ The token of the cluster. It can be viewed in the file
`doris-meta/image/VERSION`.
* `file_id`
diff --git a/docs/en/docs/admin-manual/maint-monitor/metadata-operation.md
b/docs/en/docs/admin-manual/maint-monitor/metadata-operation.md
index f71204e3b7..9ab0ec540f 100644
--- a/docs/en/docs/admin-manual/maint-monitor/metadata-operation.md
+++ b/docs/en/docs/admin-manual/maint-monitor/metadata-operation.md
@@ -36,10 +36,10 @@ For the time being, read the [Doris metadata design
document](/community/design/
## Metadata catalog structure
-Let's assume that the path of `meta_dir` specified in fe.conf is
`path/to/palo-meta`. In a normal Doris cluster, the directory structure of
metadata should be as follows:
+Let's assume that the path of `meta_dir` specified in fe.conf is
`path/to/doris-meta`. In a normal Doris cluster, the directory structure of
metadata should be as follows:
```
-/path/to/palo-meta/
+/path/to/doris-meta/
|-- bdb/
| |-- 00000000.jdb
| |-- je.config.csv
@@ -83,13 +83,13 @@ Single node FE is the most basic deployment mode. A
complete Doris cluster requi
1. First start-up
- 1. Suppose the path of `meta_dir` specified in fe.conf is
`path/to/palo-meta`.
- 2. Ensure that `path/to/palo-meta` already exists, that the permissions
are correct and that the directory is empty.
+ 1. Suppose the path of `meta_dir` specified in fe.conf is
`path/to/doris-meta`.
+ 2. Ensure that `path/to/doris-meta` already exists, that the
permissions are correct and that the directory is empty.
3. Start directly through `sh bin/start_fe.sh`.
4. After booting, you should be able to see the following log in fe.log:
* Palo FE starting...
- * image does not exist: /path/to/palo-meta/image/image.0
+ * image does not exist: /path/to/doris-meta/image/image.0
* transfer from INIT to UNKNOWN
* transfer from UNKNOWN to MASTER
* the very first time to open bdb, dbname is 1
@@ -110,10 +110,10 @@ Single node FE is the most basic deployment mode. A
complete Doris cluster requi
* Palo FE starting...
* finished to get cluster id: xxxx, role: FOLLOWER and node
name: xxxx
* If no image has been generated before reboot, you will see:
- * image does not exist: /path/to/palo-meta/image/image.0
+ * image does not exist: /path/to/doris-meta/image/image.0
* If an image is generated before the restart, you will see:
- * start load image from /path/to/palo-meta/image/image.xxx. is
ckpt: false
+ * start load image from /path/to/doris-meta/image/image.xxx. is
ckpt: false
* finished load image in xxx ms
* transfer from INIT to UNKNOWN
@@ -122,8 +122,8 @@ Single node FE is the most basic deployment mode. A
complete Doris cluster requi
* finish replay in xxx msec
* master finish replay journal, can write now.
* begin to generate new image: image.xxxx
- * start save image to /path/to/palo-meta/image/image.ckpt. is
ckpt: true
- * finished save image /path/to/palo-meta/image/image.ckpt in
xxx ms. checksum is xxxx
+ * start save image to /path/to/doris-meta/image/image.ckpt. is
ckpt: true
+ * finished save image /path/to/doris-meta/image/image.ckpt in
xxx ms. checksum is xxxx
* push image.xxx to other nodes. totally xx nodes, push
successed xx nodes
* QE service start
* thrift server started
@@ -141,7 +141,7 @@ Adding FE processes is described in detail in the [Elastic
Expansion Documents](
1. Notes
* Before adding a new FE, make sure that the current Master FE runs
properly (connection is normal, JVM is normal, image generation is normal,
bdbje data directory is too large, etc.)
- * The first time you start a new FE, you must make sure that the
`--helper` parameter is added to point to Master FE. There is no need to add
`--helper` when restarting. (If `--helper` is specified, FE will directly ask
the helper node for its role. If not, FE will try to obtain information from
`ROLE` and `VERSION` files in the `palo-meta/image/` directory.
+ * The first time you start a new FE, you must make sure that the
`--helper` parameter is added to point to Master FE. There is no need to add
`--helper` when restarting. (If `--helper` is specified, FE will directly ask
the helper node for its role. If not, FE will try to obtain information from
`ROLE` and `VERSION` files in the `doris-meta/image/` directory.
* The first time you start a new FE, you must make sure that the
`meta_dir` of the FE is created, has correct permissions and is empty.
* Starting a new FE and executing the `ALTER SYSTEM ADD
FOLLOWER/OBSERVER` statement adds FE to metadata in a sequence that is not
required. If a new FE is started first and no statement is executed, the
`current node is not added to the group. Please add it first.` in the new FE
log. When the statement is executed, it enters the normal process.
* Make sure that after the previous FE is added successfully, the next
FE is added.
@@ -151,7 +151,7 @@ Adding FE processes is described in detail in the [Elastic
Expansion Documents](
1. this need is DETACHED
- When you first start a FE to be added, if the data in
palo-meta/bdb on Master FE is large, you may see the words `this node is
DETACHED`. in the FE log to be added. At this point, bdbje is copying data, and
you can see that the `bdb/` directory of FE to be added is growing. This
process usually takes several minutes (depending on the amount of data in
bdbje). Later, there may be some bdbje-related error stack information in fe.
log. If `QE service start` and `thrift server start` are d [...]
+ When you first start a FE to be added, if the data in
doris-meta/bdb on Master FE is large, you may see the words `this node is
DETACHED`. in the FE log to be added. At this point, bdbje is copying data, and
you can see that the `bdb/` directory of FE to be added is growing. This
process usually takes several minutes (depending on the amount of data in
bdbje). Later, there may be some bdbje-related error stack information in fe.
log. If `QE service start` and `thrift server start` are [...]
2. Failure to add due to various reasons
@@ -227,7 +227,7 @@ If you need to migrate one FE from the current node to
another, there are severa
2. Single-node MASTER migration
- When there is only one FE, refer to the `Failure Recovery` section.
Copy the palo-meta directory of FE to the new node and start the new MASTER in
Step 3 of the `Failure Recovery` section
+ When there is only one FE, refer to the `Failure Recovery` section.
Copy the doris-meta directory of FE to the new node and start the new MASTER in
Step 3 of the `Failure Recovery` section
3. A set of FOLLOWER migrates from one set of nodes to another set of new nodes
diff --git a/docs/zh-CN/community/developer-guide/fe-eclipse-dev.md
b/docs/zh-CN/community/developer-guide/fe-eclipse-dev.md
index dc2b155982..9f682dcd98 100644
--- a/docs/zh-CN/community/developer-guide/fe-eclipse-dev.md
+++ b/docs/zh-CN/community/developer-guide/fe-eclipse-dev.md
@@ -160,7 +160,7 @@ FE的单元测试会首先启动一个FE服务，然后由测试用例作为客
```
mkdir /path/to/doris/fe/run/
cd /path/to/doris/fe/run/
- mkdir conf/ log/ palo-meta/
+ mkdir conf/log/doris-meta/
```
2. 创建配置文件
diff --git a/docs/zh-CN/docs/admin-manual/http-actions/fe/bootstrap-action.md
b/docs/zh-CN/docs/admin-manual/http-actions/fe/bootstrap-action.md
index 3209279319..689da335c9 100644
--- a/docs/zh-CN/docs/admin-manual/http-actions/fe/bootstrap-action.md
+++ b/docs/zh-CN/docs/admin-manual/http-actions/fe/bootstrap-action.md
@@ -42,11 +42,11 @@ under the License.
* `cluster_id`
- 集群id。可以在 `palo-meta/image/VERSION` 文件中查看。
+ 集群id。可以在 `doris-meta/image/VERSION` 文件中查看。
* `token`
- 集群token。可以在 `palo-meta/image/VERSION` 文件中查看。
+ 集群token。可以在 `doris-meta/image/VERSION` 文件中查看。
## Request body
diff --git a/docs/zh-CN/docs/admin-manual/http-actions/fe/get-small-file.md
b/docs/zh-CN/docs/admin-manual/http-actions/fe/get-small-file.md
index a7bdef5f3c..680902afb2 100644
--- a/docs/zh-CN/docs/admin-manual/http-actions/fe/get-small-file.md
+++ b/docs/zh-CN/docs/admin-manual/http-actions/fe/get-small-file.md
@@ -41,7 +41,7 @@ under the License.
* `token`
- 集群的token。可以在 `palo-meta/image/VERSION` 文件中查看。
+ 集群的token。可以在 `doris-meta/image/VERSION` 文件中查看。
* `file_id`
diff --git a/docs/zh-CN/docs/admin-manual/maint-monitor/metadata-operation.md
b/docs/zh-CN/docs/admin-manual/maint-monitor/metadata-operation.md
index 4494f767fc..db31e9edcc 100644
--- a/docs/zh-CN/docs/admin-manual/maint-monitor/metadata-operation.md
+++ b/docs/zh-CN/docs/admin-manual/maint-monitor/metadata-operation.md
@@ -36,10 +36,10 @@ under the License.
## 元数据目录结构
-我们假设在 fe.conf 中指定的 `meta_dir` 的路径为 `/path/to/palo-meta`。那么一个正常运行中的 Doris
集群，元数据的目录结构应该如下：
+我们假设在 fe.conf 中指定的 `meta_dir` 的路径为 `/path/to/doris-meta`。那么一个正常运行中的 Doris
集群，元数据的目录结构应该如下：
```
-/path/to/palo-meta/
+/path/to/doris-meta/
|-- bdb/
| |-- 00000000.jdb
| |-- je.config.csv
@@ -83,13 +83,13 @@ under the License.
1. 第一次启动
- 1. 假设在 fe.conf 中指定的 `meta_dir` 的路径为 `/path/to/palo-meta`。
- 2. 确保 `/path/to/palo-meta` 已存在，权限正确，且目录为空。
+ 1. 假设在 fe.conf 中指定的 `meta_dir` 的路径为 `/path/to/doris-meta`。
+ 2. 确保 `/path/to/doris-meta` 已存在，权限正确，且目录为空。
3. 直接通过 `sh bin/start_fe.sh` 即可启动。
4. 启动后，你应该可以在 fe.log 中看到如下日志：
* Palo FE starting...
- * image does not exist: /path/to/palo-meta/image/image.0
+ * image does not exist: /path/to/doris-meta/image/image.0
* transfer from INIT to UNKNOWN
* transfer from UNKNOWN to MASTER
* the very first time to open bdb, dbname is 1
@@ -110,10 +110,10 @@ under the License.
* Palo FE starting...
* finished to get cluster id: xxxx, role: FOLLOWER and node name: xxxx
* 如果重启前还没有 image 产生，则会看到：
- * image does not exist: /path/to/palo-meta/image/image.0
+ * image does not exist: /path/to/doris-meta/image/image.0
* 如果重启前有 image 产生，则会看到：
- * start load image from /path/to/palo-meta/image/image.xxx. is
ckpt: false
+ * start load image from /path/to/doris-meta/image/image.xxx. is
ckpt: false
* finished load image in xxx ms
* transfer from INIT to UNKNOWN
@@ -122,8 +122,8 @@ under the License.
* finish replay in xxx msec
* master finish replay journal, can write now.
* begin to generate new image: image.xxxx
- * start save image to /path/to/palo-meta/image/image.ckpt. is ckpt:
true
- * finished save image /path/to/palo-meta/image/image.ckpt in xxx ms.
checksum is xxxx
+ * start save image to /path/to/doris-meta/image/image.ckpt. is ckpt:
true
+ * finished save image /path/to/doris-meta/image/image.ckpt in xxx ms.
checksum is xxxx
* push image.xxx to other nodes. totally xx nodes, push successed xx
nodes
* QE service start
* thrift server started
@@ -141,7 +141,7 @@ under the License.
1. 注意事项
* 在添加新的 FE 之前，一定先确保当前的 Master FE 运行正常（连接是否正常，JVM 是否正常，image 生成是否正常，bdbje
数据目录是否过大等等）
- * 第一次启动新的 FE，一定确保添加了 `--helper` 参数指向 Master FE。再次启动时可不用添加
`--helper`。（如果指定了 `--helper`，FE 会直接询问 helper 节点自己的角色，如果没有指定，FE会尝试从
`palo-meta/image/` 目录下的 `ROLE` 和 `VERSION` 文件中获取信息）。
+ * 第一次启动新的 FE，一定确保添加了 `--helper` 参数指向 Master FE。再次启动时可不用添加
`--helper`。（如果指定了 `--helper`，FE 会直接询问 helper 节点自己的角色，如果没有指定，FE会尝试从
`doris-meta/image/` 目录下的 `ROLE` 和 `VERSION` 文件中获取信息）。
* 第一次启动新的 FE，一定确保这个 FE 的 `meta_dir` 已经创建、权限正确且为空。
* 启动新的 FE，和执行 `ALTER SYSTEM ADD FOLLOWER/OBSERVER` 语句在元数据添加
FE，这两个操作的顺序没有先后要求。如果先启动了新的 FE，而没有执行语句，则新的 FE 日志中会一直滚动 `current node is not
added to the group. please add it first.` 字样。当执行语句后，则会进入正常流程。
* 请确保前一个 FE 添加成功后，再添加下一个 FE。
@@ -151,7 +151,7 @@ under the License.
1. this node is DETACHED
- 当第一次启动一个待添加的 FE 时，如果 Master FE 上的 palo-meta/bdb 中的数据很大，则可能在待添加的 FE
日志中看到 `this node is DETACHED.` 字样。这时，bdbje 正在复制数据，你可以看到待添加的 FE 的 `bdb/`
目录正在变大。这个过程通常会在数分钟不等（取决于 bdbje 中的数据量）。之后，fe.log 中可能会有一些 bdbje
相关的错误堆栈信息。如果最终日志中显示 `QE service start` 和 `thrift server started`，则通常表示启动成功。可以通过
mysql-client 连接这个 FE 尝试操作。如果没有出现这些字样，则可能是 bdbje 复制日志超时等问题。这时，直接再次重启这个
FE，通常即可解决问题。
+ 当第一次启动一个待添加的 FE 时，如果 Master FE 上的 doris-meta/bdb 中的数据很大，则可能在待添加的 FE
日志中看到 `this node is DETACHED.` 字样。这时，bdbje 正在复制数据，你可以看到待添加的 FE 的 `bdb/`
目录正在变大。这个过程通常会在数分钟不等（取决于 bdbje 中的数据量）。之后，fe.log 中可能会有一些 bdbje
相关的错误堆栈信息。如果最终日志中显示 `QE service start` 和 `thrift server started`，则通常表示启动成功。可以通过
mysql-client 连接这个 FE 尝试操作。如果没有出现这些字样，则可能是 bdbje 复制日志超时等问题。这时，直接再次重启这个
FE，通常即可解决问题。
2. 各种原因导致添加失败
@@ -227,7 +227,7 @@ FE 有可能因为某些原因出现无法启动 bdbje、FE 之间无法同步
2. 单节点 MASTER 迁移
- 当只有一个 FE 时，参考 `故障恢复` 一节。将 FE 的 palo-meta 目录拷贝到新节点上，按照 `故障恢复`
一节中，步骤3的方式启动新的 MASTER
+ 当只有一个 FE 时，参考 `故障恢复` 一节。将 FE 的 doris-meta 目录拷贝到新节点上，按照 `故障恢复`
一节中，步骤3的方式启动新的 MASTER
3. 一组 FOLLOWER 从一组节点迁移到另一组新的节点
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
