Installing DB2 on the primary node.
在主节点上安装db2。
Enter the hostname of the primary node.
输入主节点的主机名。
Every node has one and only one primary node type.
每个节点都有且只有一个主节点类型。
The middle column should be the hostname of the primary node.
中间一列应该是主节点的主机名。
Upon failure of the primary node the redundant node takes over.
在主节点发生故障时，冗余节点可以接管。
Create the DB2 users and groups on the primary node (Node1) and enter.
按照以下步骤在主节点上创建DB2用户和组。
Selecting the primary option installs a primary node and creates a cluster.
选择主选项会安装一个主节点并创建一个集群。
Use the ps command to make sure WebSphere MQ is running on the primary node.
可以使用ps命令来确认WebSphereMQ正在主节点上运行。
There can be up to 7 servers in a cluster, and any node can be the primary node.
一个集群最多可以支持7个服务器，并且任意节点都可以是主节点。
Use the ps command to make sure LoadLeveler daemons are running on the primary node.
通过ps命令确认LoadLeveler后台进程正在在主节点上运行。
Use the ps command to make sure the Web server daemons are running on the primary node.
使用ps命令来确保Web服务器后台进程正在主节点上运行。
In the case of an e-commerce system, the primary node could be either an order or a customer.
如在一个电子商务系统中，主要节点可以是一个订单或者一个客户。
Note that I am using the cluster address in the above URLs and not the address of the primary node.
注意，在上面我使用的是群集地址，而不是主节点的地址。
The reason is that the copy on the secondary node is still pointing to the repository of the primary node.
原因在于，次节点上的副本仍然指向主节点的存储库。
The secondary node is promoted to primary if the clustering solution detects that the primary node is down.
如果集群解决方案检测到主节点故障，辅助节点升为主节点。
The DB2 database installed with the primary node is automatically used by all other nodes in the cluster.
与主节点安装在一起的DB 2数据库自动被集群中所有其他节点使用。
On the primary node (ha1) create a highly available queue manager using the command shown below (as root).
在主节点(ha1)上使用下面的命令创建一个高可用的队列管理器(以root身份)。
Allow the secondary node to access objects backed up on the primary node (this has to be done on the primary machine).
允许辅助节点访问备份在主节点上的对象(必须在主机器上完成)。
All writes are directed to the primary node, from where they are replicated while reads can be performed on any node.
所有的写操作都被分发到主节点，而读操作可以在任何节点上进行。
Migration is simply a failover that never fails back, and scaling up is a failover in which the primary node never goes offline.
迁移不过就是永不退回的故障转移，扩展是永远不将主节点置于离线的故障转移。
In this error scenario, the communication link fails between the nodes, and both nodes believe that they are the primary node.
在这个错误场景中，节点之间的通信链发生故障，每个节点都认为自己是主节点。
This output shows that the application is successfully running on the WAS node ha, which is being run on the primary node ha1.
输出表明，应用程序正在WAS节点ha上成功地运行，而WAS节点ha是在主节点ha1上运行。
A primary node type defines the characteristics of the node, such as the properties and child nodes that the node is allowed to have.
主节点类型定义了节点的特征，例如允许节点拥有的属性和子节点。
Write operations occur through the primary node and are performed to the local storage and secondary storage simultaneously (see Figure 3).
写操作从主节点开始进行，同时执行本地存储和辅助存储(见图3)。
Once everything is configured on the primary node (node1), we need to synchronize this with all other nodes in the cluster. To do that, do the following.
在主节点(在这里是node1)上完成所有配置之后，需要让集群中的所有其他节点与它同步。
Because driver maintains connection to both nodes while write transactions are directed to the primary node, read transactions can be directed to either node.
由于驱动程序维护与两个节点的连接，同时写事务被定向到主节点，因此读事务可以定向到任何一个节点。
It's still possible to lose data (for example, if both nodes failed), but failure of the primary node will not cause data loss, because the data has been replicated.
这仍然可能丢失数据(例如，如果两个节点都发生故障)，但是主节点故障不会引起数据丢失，因为数据已经被复制了。
If you have configured a primary node (that is, one that is favored to gain the floating resource above all others), it will regain the floating resources automatically.
如果您配置了一个主节点(即，一个可以优先于其他节点获得浮动资源的节点)，它将自动重新获得浮动资源。
This article assumes that we have a two-node cluster with Node1 as the primary node and Node2 as the failover/fallover/takeover/stand-by/secondary node, as shown below in Figure 1.
本文假设集群中有两个节点，Node1是主节点，Node2 是故障转移/接管/备用/辅助节点，见图 1。
The increasing CPU utilization is attributed to unnecessary node hops for interrupts being taken on Ethernet adapters on non-primary nodes but being processed on CPUs on the primary node.
CPU利用率快速增加的原因是，在非主节点上的以太网适配器中接收的中断却在主节点的CPU 上处理，这导致了不必要的节点跳转。
应用推荐