在主节点上安装db2。
对主节点使用puttyto ssh。
主节点收集结果，并继续分发任务，依此类推。
The master node assembles the results, further distributes work, and so on.
补充操作在主节点恢复时退回主节点。
The complementary action is to failback when the primary node is recovered.
在典型的设置中，应用程序在主节点上开始运行。
In a typical setup, the master node is where the applications are initiated.
将目录与文件从主节点复制到克隆节点。
Copy directories and files from main node to the clone node.
在主节点发生故障时，冗余节点可以接管。
Upon failure of the primary node the redundant node takes over.
这个节点不必是主节点。
命令输出指出主节点和从节点上的一些日志。
The command output indicates some logs located on the master and slaves.
选择主选项会安装一个主节点并创建一个集群。
Selecting the primary option installs a primary node and creates a cluster.
重新启动主节点上的heartbeat服务。
注意，在上面我使用的是群集地址，而不是主节点的地址。
Note that I am using the cluster address in the above URLs and not the address of the primary node.
行5继续定义主节点和当前节点之间的边的属性。
Line 5 proceeds with defining the attributes of the edge between the home node and the current node.
最后，声明这个节点是集群中的主节点：tyd。
Last, announce this node as the master node in the cluster: tyd.
向下扩展就像退回操作，其中没有将主节点置于在线的任务。
Scaling down is like a failback operation without the task of bringing the primary node up.
主节点负责根据需要将应用程序迁移到从属节点上。
It's the master node's responsibility to migrate applications to the drones when required.
工作者节点处理这些小任务，把结果返回给主节点。
The worker node processes that smaller task, and passes the answer back to the master node.
每个仓库都必须支持主节点类型nt：base。
Every repository must support the primary node type, nt: base. There are a number of other common node types that a repository may support.
原因在于，次节点上的副本仍然指向主节点的存储库。
The reason is that the copy on the secondary node is still pointing to the repository of the primary node.
在这类集群中，除了主节点以外，不需要在从节点上运行GUI。
In such a cluster, apart from the master node, you don't need to run a GUI on the slaves.
rac主节点和辅助节点将在数据源url中按位置指定。
The primary and secondary RAC nodes are specified positionally in the data source URL.
这表明失效切换到主节点后，更新的配置信息保存了下来。
This shows that the updated configuration information survived a failover to the primary.
写操作从主节点开始进行，同时执行本地存储和辅助存储(见图3)。
Write operations occur through the primary node and are performed to the local storage and secondary storage simultaneously (see Figure 3).
管理节点安装主节点和备份节点，并根据需要进行软件更新。
The management node installs both the master and backup nodes and provides software updates as required.
如果集群解决方案检测到主节点故障，辅助节点升为主节点。
The secondary node is promoted to primary if the clustering solution detects that the primary node is down.
GPFS允许主节点和备份节点并发访问集群中的所有文件。
GPFS allows both the master and backup nodes to have concurrent access to all of the files in the cluster.
与主节点安装在一起的DB 2数据库自动被集群中所有其他节点使用。
The DB2 database installed with the primary node is automatically used by all other nodes in the cluster.
然后将这些子问题发布给工作节点，由它处理后再将结果返回给主节点。
These subproblems are then distributed to worker nodes, which solve the problem and return the results to the master node.
主节点和备份节点连接到一台IBMDS4500存储服务器。
The master and the backup node is connected to an IBM DS4500 storage server.
主节点和备份节点连接到一台IBMDS4500存储服务器。
The master and the backup node is connected to an IBM DS4500 storage server.
应用推荐