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 00fd5b1b1c [typo](doc) update Paxos spell mistake (#15171)
00fd5b1b1c is described below
commit 00fd5b1b1cc064a45ca1d1a73c6bef45003bacae
Author: gnehil <[email protected]>
AuthorDate: Fri Dec 23 16:47:12 2022 +0800
[typo](doc) update Paxos spell mistake (#15171)
---
docs/en/docs/faq/install-faq.md | 2 +-
docs/zh-CN/docs/faq/install-faq.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/en/docs/faq/install-faq.md b/docs/en/docs/faq/install-faq.md
index 5ec4501485..0f722407e7 100644
--- a/docs/en/docs/faq/install-faq.md
+++ b/docs/en/docs/faq/install-faq.md
@@ -51,7 +51,7 @@ The reason why the CIDR format is used instead of specifying
a specific IP direc
First of all, make it clear that FE has only two roles: Follower and Observer.
The Master is just an FE selected from a group of Follower nodes. Master can be
regarded as a special kind of Follower. So when we were asked how many FEs a
cluster had and what roles they were, the correct answer should be the number
of all FE nodes, the number of Follower roles and the number of Observer roles.
-All FE nodes of the Follower role will form an optional group, similar to the
group concept in the Poxas consensus protocol. A Follower will be elected as
the Master in the group. When the Master hangs up, a new Follower will be
automatically selected as the Master. The Observer will not participate in the
election, so the Observer will not be called Master.
+All FE nodes of the Follower role will form an optional group, similar to the
group concept in the Paxos consensus protocol. A Follower will be elected as
the Master in the group. When the Master hangs up, a new Follower will be
automatically selected as the Master. The Observer will not participate in the
election, so the Observer will not be called Master.
A metadata log needs to be successfully written in most Follower nodes to be
considered successful. For example, if there are 3 FEs, only 2 can be
successfully written. This is why the number of Follower roles needs to be an
odd number.
diff --git a/docs/zh-CN/docs/faq/install-faq.md
b/docs/zh-CN/docs/faq/install-faq.md
index 3b96414630..c5c73ec4f8 100644
--- a/docs/zh-CN/docs/faq/install-faq.md
+++ b/docs/zh-CN/docs/faq/install-faq.md
@@ -51,7 +51,7 @@ priorty_network 的值是 CIDR 格式表示的。分为两部分，第一部分
首先明确一点，FE 只有两种角色：Follower 和 Observer。而 Master 只是一组 Follower 节点中选择出来的一个
FE。Master 可以看成是一种特殊的 Follower。所以当我们被问及一个集群有多少 FE，都是什么角色时，正确的回答当时应该是所有 FE
节点的个数，以及 Follower 角色的个数和 Observer 角色的个数。
-所有 Follower 角色的 FE 节点会组成一个可选择组，类似 Poxas 一致性协议里的组概念。组内会选举出一个 Follower 作为
Master。当 Master 挂了，会自动选择新的 Follower 作为 Master。而 Observer 不会参与选举，因此 Observer
也不会称为 Master 。
+所有 Follower 角色的 FE 节点会组成一个可选择组，类似 Paxos 一致性协议里的组概念。组内会选举出一个 Follower 作为
Master。当 Master 挂了，会自动选择新的 Follower 作为 Master。而 Observer 不会参与选举，因此 Observer
也不会称为 Master 。
一条元数据日志需要在多数 Follower 节点写入成功，才算成功。比如3个 FE ，2个写入成功才可以。这也是为什么 Follower
角色的个数需要是奇数的原因。
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
