This example presents a simple ha cluster that consists of three nodes: a master node, a backup node, and a management node.
本例描述了一个简单的ha集群，由三个节点构成：一个主节点，一个备份节点，以及一个管理节点。
Performs configuration synchronization between the master repository and the node repository, thus bringing the updated application down to the node.
在主存储库与节点存储库间执行配置同步，以将已更新的应用程序部署到该节点。
During failover, one of the children becomes the master node and all replication starts flowing from that node.
在故障恢复过程中，其中一个子节点会成为主节点，而所有复制将从该节点开始。
If you only provision a Hadoop Master node, and therefore only work on that single node, you are working in pseudo-distributed mode.
如果您只提供一个HadoopMaster节点，那么只能在一个节点上工作，即在伪分布模式下工作。
When the master repository configuration is synchronized with a node, the application configuration is replicated in the node level repository and extracted in the application install destination.
当主存储配置与节点同步后，应用程序配置将复制到节点级别的存储库中，并提取到应用程序安装目的地中。
The worker node processes that smaller task, and passes the answer back to the master node.
工作者节点处理这些小任务，把结果返回给主节点。
In a two-node cluster, when one fails or the network connection snaps, each node believes that it is the master and starts interacting with the outside world.
在一个2节点集群中，当一个节点发生故障或网络连接中断，每个节点都会充当主要节点并开始与外界交互。
Hadoop's Name node and Job tracker reside on the master node and might not need scaling at this stage.
Hadoop的命名节点和工作跟踪器贮存在主节点上，在这个阶段可能并不需要扩充。
The --verify option verifies the tables, columns, data types, and so forth between the master node and the node on which the template is being realized.
verify选项检验主节点和当前在被实现的节点之间的表、列、数据类型，等等。
This paper detailedly introduces the expander node configuration method and the master node software design method.
详细介绍扩展节点的配置方法和主节点的软件设计方法。
Expand the master table node and select the detail node for the related table.
展开主资料表节点，并选取相关资料表的详细资料节点。
Expand the master table node and select the detail node for the related table.
展开主资料表节点，并选取相关资料表的详细资料节点。
应用推荐