From 7fe281b7a64b024a4ea4e987204c6ed6175a648d Mon Sep 17 00:00:00 2001 From: FreeOnePlus <54164178+FreeOnePlus@users.noreply.github.com> Date: Tue, 18 Apr 2023 10:43:53 +0800 Subject: [PATCH] [docs](docs)Modify the wrong information about the concept description in the document (#18760) --- .../cluster-management/elastic-expansion.md | 16 ++++++++-------- .../cluster-management/elastic-expansion.md | 16 ++++++++-------- 2 files changed, 16 insertions(+), 16 deletions(-) diff --git a/docs/en/docs/admin-manual/cluster-management/elastic-expansion.md b/docs/en/docs/admin-manual/cluster-management/elastic-expansion.md index e8cc4c5de8..7f2165d50a 100644 --- a/docs/en/docs/admin-manual/cluster-management/elastic-expansion.md +++ b/docs/en/docs/admin-manual/cluster-management/elastic-expansion.md @@ -47,17 +47,17 @@ The process of FE node expansion and contraction does not affect the current sys ### Adding FE nodes -FE is divided into three roles: Leader, Follower and Observer. By default, a cluster can have only one Leader and multiple Followers and Observers. Leader and Follower form a Paxos selection group. If the Leader goes down, the remaining Followers will automatically select a new Leader to ensure high write availability. Observer synchronizes Leader data, but does not participate in the election. If only one FE is deployed, FE defaults to Leader. +FE is divided into two roles: Follower and Observer. The Follower role will elect a Follower node as the Master. By default, a cluster can only have one Follower role in the Master state, and there can be multiple Followers and Observers. At the same time, it is necessary to ensure that there are an odd number of Follower roles. All Follower roles form an election group. If the Follower in the Master state goes down, the remaining Followers will automatically elect a new Master to ensure high write availability. Observer synchronizes the data of Master, but does not participate in the election. If only one FE is deployed, the FE is the Master by default. -The first FE to start automatically becomes Leader. On this basis, several Followers and Observers can be added. +The first FE to start automatically becomes Master. On this basis, several Followers and Observers can be added. #### Configure and start Follower or Observer. - Follower and Observer are configured with Leader. The following commands need to be executed at the first startup: + Follower and Observer are configured with Master. The following commands need to be executed at the first startup: `bin/start_fe.sh --helper host:edit_log_port --daemon` -The host is the node IP of Leader, and the edit\_log\_port in Lead's configuration file fe.conf. The --helper is only required when follower/observer is first startup. +The host is the node IP of Master, and the edit\_log\_port in Lead's configuration file fe.conf. The --helper is only required when follower/observer is first startup. #### Add Follower or Observer to the cluster @@ -79,8 +79,8 @@ You can view the FE currently joined the cluster and its corresponding roles. > Notes for FE expansion: > -> 1. The number of Follower FEs (including Leaders) must be odd. It is recommended that a maximum of three constituent high availability (HA) modes be deployed. -> 2. When FE is in a highly available deployment (1 Leader, 2 Follower), we recommend that the reading service capability of FE be extended by adding Observer FE. Of course, you can continue to add Follower FE, but it's almost unnecessary. +> 1. The number of Follower FEs (including Masters) must be odd. It is recommended that a maximum of three constituent high availability (HA) modes be deployed. +> 2. When FE is in a highly available deployment (1 Master, 2 Follower), we recommend that the reading service capability of FE be extended by adding Observer FE. Of course, you can continue to add Follower FE, but it's almost unnecessary. > 3. Usually a FE node can handle 10-20 BE nodes. It is suggested that the total number of FE nodes should be less than 10. Usually three can meet most of the needs. > 4. The helper cannot point to the FE itself, it must point to one or more existing running Master/Follower FEs. @@ -92,11 +92,11 @@ Delete the corresponding FE node using the following command: > Notes for FE contraction: > -> 1. When deleting Follower FE, make sure that the remaining Follower (including Leader) nodes are odd. +> 1. When deleting Follower FE, make sure that the remaining Follower (including Master) nodes are odd. ## BE Scaling -Users can login to Leader FE through mysql-client. By: +Users can login to Master FE through mysql-client. By: ```SHOW PROC '/backends';``` diff --git a/docs/zh-CN/docs/admin-manual/cluster-management/elastic-expansion.md b/docs/zh-CN/docs/admin-manual/cluster-management/elastic-expansion.md index ce8b8152b5..494cc30a0c 100644 --- a/docs/zh-CN/docs/admin-manual/cluster-management/elastic-expansion.md +++ b/docs/zh-CN/docs/admin-manual/cluster-management/elastic-expansion.md @@ -47,19 +47,19 @@ FE 节点的扩容和缩容过程，不影响当前系统运行。 ### 增加 FE 节点 -FE 分为 Leader，Follower 和 Observer 三种角色。 默认一个集群，只能有一个 Leader，可以有多个 Follower 和 Observer。其中 Leader 和 Follower 组成一个 Paxos 选择组，如果 Leader 宕机，则剩下的 Follower 会自动选出新的 Leader，保证写入高可用。Observer 同步 Leader 的数据，但是不参加选举。如果只部署一个 FE，则 FE 默认就是 Leader。 +FE 分为 Follower 和 Observer 两种角色，其中 Follower 角色会选举出一个 Follower 节点作为 Master。 默认一个集群，只能有一个 Master 状态的 Follower 角色，可以有多个 Follower 和 Observer，同时需保证 Follower 角色为奇数个。其中所有 Follower 角色组成一个选举组，如果 Master 状态的 Follower 宕机，则剩下的 Follower 会自动选出新的 Master，保证写入高可用。Observer 同步 Master 的数据，但是不参加选举。如果只部署一个 FE，则 FE 默认就是 Master。 -第一个启动的 FE 自动成为 Leader。在此基础上，可以添加若干 Follower 和 Observer。 +第一个启动的 FE 自动成为 Master。在此基础上，可以添加若干 Follower 和 Observer。 #### 配置及启动 Follower 或 Observer -这里 Follower 和 Observer 的配置同 Leader 的配置。 +这里 Follower 和 Observer 的配置同 Master 的配置。 首先第一次启动时，需执行以下命令： `./bin/start_fe.sh --helper leader_fe_host:edit_log_port --daemon` -其中 leader\_fe\_host 为 Leader 所在节点 ip, edit\_log\_port 在 Leader 的配置文件 fe.conf 中。--helper 参数仅在 follower 和 observer 第一次启动时才需要。 +其中 leader\_fe\_host 为 Master 所在节点 ip, edit\_log\_port 在 Master 的配置文件 fe.conf 中。--helper 参数仅在 follower 和 observer 第一次启动时才需要。 #### 将 Follower 或 Observer 加入到集群 @@ -76,8 +76,8 @@ FE 分为 Leader，Follower 和 Observer 三种角色。 默认一个集群， 查看 Follower 或 Observer 运行状态。使用 mysql-client 连接到任一已启动的 FE，并执行：SHOW PROC '/frontends'; 可以查看当前已加入集群的 FE 及其对应角色。 > FE 扩容注意事项： -> 1. Follower FE（包括 Leader）的数量必须为奇数，建议最多部署 3 个组成高可用（HA）模式即可。 -> 2. 当 FE 处于高可用部署时（1个 Leader，2个 Follower），我们建议通过增加 Observer FE 来扩展 FE 的读服务能力。当然也可以继续增加 Follower FE，但几乎是不必要的。 +> 1. Follower FE（包括 Master）的数量必须为奇数，建议最多部署 3 个组成高可用（HA）模式即可。 +> 2. 当 FE 处于高可用部署时（1个 Master，2个 Follower），我们建议通过增加 Observer FE 来扩展 FE 的读服务能力。当然也可以继续增加 Follower FE，但几乎是不必要的。 > 3. 通常一个 FE 节点可以应对 10-20 台 BE 节点。建议总的 FE 节点数量在 10 个以下。而通常 3 个即可满足绝大部分需求。 > 4. helper 不能指向 FE 自身，必须指向一个或多个已存在并且正常运行中的 Master/Follower FE。 @@ -88,11 +88,11 @@ FE 分为 Leader，Follower 和 Observer 三种角色。 默认一个集群， ```ALTER SYSTEM DROP FOLLOWER[OBSERVER] "fe_host:edit_log_port";``` > FE 缩容注意事项： -> 1. 删除 Follower FE 时，确保最终剩余的 Follower（包括 Leader）节点为奇数。 +> 1. 删除 Follower FE 时，确保最终剩余的 Follower（包括 Master）节点为奇数。 ## BE 扩容和缩容 -用户可以通过 mysql-client 登陆 Leader FE。通过: +用户可以通过 mysql-client 登陆 Master FE。通过: ```SHOW PROC '/backends';```