wangtianyi2004 commented on code in PR #1664: URL: https://github.com/apache/doris-website/pull/1664#discussion_r1899985092
########## docs/admin-manual/cluster-management/elastic-expansion.md: ########## @@ -24,131 +24,123 @@ KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> +Doris supports online elastic scaling, allowing users to dynamically add or remove nodes without interrupting services. This capability ensures businesses can meet growing demands or reduce idle resource waste. Scaling up or down BE nodes does not affect cluster availability but involves data migration, so it is recommended to perform scaling operations during periods of low business activity. -# Elastic scaling +## Scale In/Out the FE Clusters -Doris can easily expand and shrink FE, BE, Broker instances. +Doris FE nodes are divided into the following three roles, with each FE node containing a full set of metadata: -## FE Scaling +* Master Node: Responsible for reading and writing metadata. When metadata changes occur on the Master node, they are synchronized to non-Master nodes via the BDB JE protocol. There can be only one Master FE node in the cluster. -High availability of FE can be achieved by expanding FE to three top-one nodes. +* Follower Node: Responsible for reading metadata. In the event of a Master node failure, Follower nodes initiate a leader election to select a new Master node. Within the cluster, the total number of Master and Follower nodes is recommended to be an odd number. -Users can login to Master FE through MySQL client. By: +* Observer Node: Responsible for reading metadata but does not participate in leader election. It is used to extend the read service capacity of FE nodes. -`SHOW PROC '/frontends';` +Typically, each FE node can handle the load operations of 10-20 BE nodes. A configuration of 3 FE nodes is sufficient to meet the requirements of most business scenarios. -To view the current FE node situation. -You can also view the FE node through the front-end page connection: ``http://fe_hostname:fe_http_port/frontend`` or ```http://fe_hostname:fe_http_port/system?Path=//frontends```. +### Scale the FE out -All of the above methods require Doris's root user rights. +::: info Note: Review Comment: done ########## i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/cluster-management/elastic-expansion.md: ########## @@ -27,144 +27,117 @@ under the License. -Doris 可以很方便的扩容和缩容 FE、BE、Broker 实例。 +Doris 支持在线弹性扩容，过动态添加或移除节点，用户无需中断服务即可满足业务增长需求或降低空闲资源的浪费。扩缩容 BE 节点时，不影响集群可用性，但会涉及到数据搬迁，建议在业务闲事进行扩缩容操作。 Review Comment: done ########## i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/cluster-management/elastic-expansion.md: ########## @@ -27,144 +27,117 @@ under the License. -Doris 可以很方便的扩容和缩容 FE、BE、Broker 实例。 +Doris 支持在线弹性扩容，过动态添加或移除节点，用户无需中断服务即可满足业务增长需求或降低空闲资源的浪费。扩缩容 BE 节点时，不影响集群可用性，但会涉及到数据搬迁，建议在业务闲事进行扩缩容操作。 -## FE 扩容和缩容 +## 扩缩容 FE 集群 -可以通过将 FE 扩容至 3 个以上节点来实现 FE 的高可用。 +Doris 的 FE 节点分为以下三种角色，每一个 FE 节点都有全量的元数据信息： -用户可以通过 MySQL 客户端登陆 Master FE。通过： +* Master 节点：负责元数据的读写操作，当 Master 的元数据发生变化，会通过 BDB JE 协议同步到非 Master 几点中，统一集群中只能有一个 Master FE 节点； Review Comment: done -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org For additional commands, e-mail: commits-h...@doris.apache.org
