This is an automated email from the ASF dual-hosted git repository.
luzhijing pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git
The following commit(s) were added to refs/heads/master by this push:
new f92494417e49 fix the startup of fe (#521)
f92494417e49 is described below
commit f92494417e49d37cab72ea5c945d911bdf171514
Author: echo-dundun <[email protected]>
AuthorDate: Mon Apr 8 19:07:52 2024 +0800
fix the startup of fe (#521)
---
docs/admin-manual/maint-monitor/metadata-operation.md | 2 +-
.../current/admin-manual/maint-monitor/metadata-operation.md | 2 +-
.../version-2.0/admin-manual/maint-monitor/metadata-operation.md | 2 +-
.../version-2.1/admin-manual/maint-monitor/metadata-operation.md | 2 +-
.../version-2.0/admin-manual/maint-monitor/metadata-operation.md | 2 +-
.../version-2.1/admin-manual/maint-monitor/metadata-operation.md | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/docs/admin-manual/maint-monitor/metadata-operation.md
b/docs/admin-manual/maint-monitor/metadata-operation.md
index 45a0dd992d78..7042914e3c9f 100644
--- a/docs/admin-manual/maint-monitor/metadata-operation.md
+++ b/docs/admin-manual/maint-monitor/metadata-operation.md
@@ -192,7 +192,7 @@ FE may fail to start bdbje and synchronize between FEs for
some reasons. Phenome
1. Modify fe.conf
- If the node is an OBSERVER, first change the `role=OBSERVER` in the
`meta_dir/image/ROLE` file to `role=FOLLOWER`. (Recovery from the OBSERVER node
will be more cumbersome, first follow the steps here, followed by a separate
description)
- If fe.version < 2.0.2, add configuration in fe.conf:
`metadata_failure_recovery=true`.
- 2. Run `sh bin/start_fe.sh --metadata_failure_recovery` to start the FE
+ 2. Run `sh bin/start_fe.sh --metadata_failure_recovery --daemon` to
start the FE
3. If normal, the FE will start in the role of MASTER, similar to the
description in the previous section `Start a single node FE`. You should see
the words `transfer from XXXX to MASTER` in fe.log.
4. After the start-up is completed, connect to the FE first, and
execute some query imports to check whether normal access is possible. If the
operation is not normal, it may be wrong. It is recommended to read the above
steps carefully and try again with the metadata previously backed up. If not,
the problem may be more serious.
5. If successful, through the `show frontends;` command, you should see
all the FEs you added before, and the current FE is master.
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/maint-monitor/metadata-operation.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/maint-monitor/metadata-operation.md
index e0963eccbcd6..f72fd6962350 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/maint-monitor/metadata-operation.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/maint-monitor/metadata-operation.md
@@ -192,7 +192,7 @@ FE 有可能因为某些原因出现无法启动 bdbje、FE 之间无法同步
1. 修改 `fe.conf`
- 如果该节点是一个 OBSERVER，先将 `meta_dir/image/ROLE` 文件中的 `role=OBSERVER` 改为
`role=FOLLOWER`。（从 OBSERVER 节点恢复会比较麻烦，先按这里的步骤操作，后面会有单独说明）)
- 如果 FE 版本< 2.0.2, 则还需要在 fe.conf 中添加配置：`metadata_failure_recovery=true`。
- 2. 执行 `sh bin/start_fe.sh --metadata_failure_recovery` 启动这个 FE。
+ 2. 执行 `sh bin/start_fe.sh --metadata_failure_recovery --daemon` 启动这个 FE。
3. 如果正常，这个 FE 会以 MASTER 的角色启动，类似于前面 `启动单节点 FE` 一节中的描述。在 fe.log 应该会看到
`transfer from XXXX to MASTER` 等字样。
4. 启动完成后，先连接到这个
FE，执行一些查询导入，检查是否能够正常访问。如果不正常，有可能是操作有误，建议仔细阅读以上步骤，用之前备份的元数据再试一次。如果还是不行，问题可能就比较严重了。
5. 如果成功，通过 `show frontends;` 命令，应该可以看到之前所添加的所有 FE，并且当前 FE 是 master。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/admin-manual/maint-monitor/metadata-operation.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/admin-manual/maint-monitor/metadata-operation.md
index 85357b2266ae..00d01a0ac80d 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/admin-manual/maint-monitor/metadata-operation.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/admin-manual/maint-monitor/metadata-operation.md
@@ -224,7 +224,7 @@ FE 有可能因为某些原因出现无法启动 bdbje、FE 之间无法同步
- 如果该节点是一个 OBSERVER，先将 `meta_dir/image/ROLE` 文件中的 `role=OBSERVER` 改为
`role=FOLLOWER`。（从 OBSERVER 节点恢复会比较麻烦，先按这里的步骤操作，后面会有单独说明）)
- 如果 FE 版本< 2.0.2, 则还需要在 fe.conf 中添加配置：`metadata_failure_recovery=true`。
- 2. 执行 `sh bin/start_fe.sh --metadata_failure_recovery` 启动这个 FE。
+ 2. 执行 `sh bin/start_fe.sh --metadata_failure_recovery --daemon` 启动这个 FE。
3. 如果正常，这个 FE 会以 MASTER 的角色启动，类似于前面 `启动单节点 FE` 一节中的描述。在 fe.log 应该会看到
`transfer from XXXX to MASTER` 等字样。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/maint-monitor/metadata-operation.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/maint-monitor/metadata-operation.md
index e0963eccbcd6..f72fd6962350 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/maint-monitor/metadata-operation.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/admin-manual/maint-monitor/metadata-operation.md
@@ -192,7 +192,7 @@ FE 有可能因为某些原因出现无法启动 bdbje、FE 之间无法同步
1. 修改 `fe.conf`
- 如果该节点是一个 OBSERVER，先将 `meta_dir/image/ROLE` 文件中的 `role=OBSERVER` 改为
`role=FOLLOWER`。（从 OBSERVER 节点恢复会比较麻烦，先按这里的步骤操作，后面会有单独说明）)
- 如果 FE 版本< 2.0.2, 则还需要在 fe.conf 中添加配置：`metadata_failure_recovery=true`。
- 2. 执行 `sh bin/start_fe.sh --metadata_failure_recovery` 启动这个 FE。
+ 2. 执行 `sh bin/start_fe.sh --metadata_failure_recovery --daemon` 启动这个 FE。
3. 如果正常，这个 FE 会以 MASTER 的角色启动，类似于前面 `启动单节点 FE` 一节中的描述。在 fe.log 应该会看到
`transfer from XXXX to MASTER` 等字样。
4. 启动完成后，先连接到这个
FE，执行一些查询导入，检查是否能够正常访问。如果不正常，有可能是操作有误，建议仔细阅读以上步骤，用之前备份的元数据再试一次。如果还是不行，问题可能就比较严重了。
5. 如果成功，通过 `show frontends;` 命令，应该可以看到之前所添加的所有 FE，并且当前 FE 是 master。
diff --git
a/versioned_docs/version-2.0/admin-manual/maint-monitor/metadata-operation.md
b/versioned_docs/version-2.0/admin-manual/maint-monitor/metadata-operation.md
index bb53e34c5d0a..44cde47f605b 100644
---
a/versioned_docs/version-2.0/admin-manual/maint-monitor/metadata-operation.md
+++
b/versioned_docs/version-2.0/admin-manual/maint-monitor/metadata-operation.md
@@ -192,7 +192,7 @@ FE may fail to start bdbje and synchronize between FEs for
some reasons. Phenome
1. Modify fe.conf
- If the node is an OBSERVER, first change the `role=OBSERVER` in the
`meta_dir/image/ROLE` file to `role=FOLLOWER`. (Recovery from the OBSERVER node
will be more cumbersome, first follow the steps here, followed by a separate
description)
- If fe.version < 2.0.2, add configuration in fe.conf:
`metadata_failure_recovery=true`.
- 2. Run `sh bin/start_fe.sh --metadata_failure_recovery` to start the FE
+ 2. Run `sh bin/start_fe.sh --metadata_failure_recovery --daemon` to
start the FE
3. If normal, the FE will start in the role of MASTER, similar to the
description in the previous section `Start a single node FE`. You should see
the words `transfer from XXXX to MASTER` in fe.log.
4. After the start-up is completed, connect to the FE first, and
execute some query imports to check whether normal access is possible. If the
operation is not normal, it may be wrong. It is recommended to read the above
steps carefully and try again with the metadata previously backed up. If not,
the problem may be more serious.
5. If successful, through the `show frontends;` command, you should see
all the FEs you added before, and the current FE is master.
diff --git
a/versioned_docs/version-2.1/admin-manual/maint-monitor/metadata-operation.md
b/versioned_docs/version-2.1/admin-manual/maint-monitor/metadata-operation.md
index 45a0dd992d78..7042914e3c9f 100644
---
a/versioned_docs/version-2.1/admin-manual/maint-monitor/metadata-operation.md
+++
b/versioned_docs/version-2.1/admin-manual/maint-monitor/metadata-operation.md
@@ -192,7 +192,7 @@ FE may fail to start bdbje and synchronize between FEs for
some reasons. Phenome
1. Modify fe.conf
- If the node is an OBSERVER, first change the `role=OBSERVER` in the
`meta_dir/image/ROLE` file to `role=FOLLOWER`. (Recovery from the OBSERVER node
will be more cumbersome, first follow the steps here, followed by a separate
description)
- If fe.version < 2.0.2, add configuration in fe.conf:
`metadata_failure_recovery=true`.
- 2. Run `sh bin/start_fe.sh --metadata_failure_recovery` to start the FE
+ 2. Run `sh bin/start_fe.sh --metadata_failure_recovery --daemon` to
start the FE
3. If normal, the FE will start in the role of MASTER, similar to the
description in the previous section `Start a single node FE`. You should see
the words `transfer from XXXX to MASTER` in fe.log.
4. After the start-up is completed, connect to the FE first, and
execute some query imports to check whether normal access is possible. If the
operation is not normal, it may be wrong. It is recommended to read the above
steps carefully and try again with the metadata previously backed up. If not,
the problem may be more serious.
5. If successful, through the `show frontends;` command, you should see
all the FEs you added before, and the current FE is master.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
