在管理节点上有对每个计算节点的定义。
Definitions for each of the compute nodes exist on the management node.
可以在这些节点之间添加任何转换节点，以支持对每个记录进行修改。
Any transformation node could be added between these nodes to enable the modification of each file record.
但是对我们而言却是极好的，因为这意味着没有人可以通过查看一个节点或者甚至一组节点计算出系统的具体作用。
But it's perfect for us, because it means that nobody can work out what the system is doing by looking at one node, or even a group of nodes.
随着对每个节点进行增量升级，单元的中央配置存储库将包含进版本5和版本6节点的文档。
As the incremental upgrade proceeds on each node, the cell's central configuration repository will contain documents for both V5 and V6 nodes.
图1显示了内容模型的示例，在该示例中，当前用户仅拥有对某些子树节点(从节点1.2开始)的“查看”权限。
Figure 1 shows an example of a content model in which the current user possesses only VIEW rights to some of the nodes of the sub-tree, starting at node 1.2.
也许您更愿意对原来的节点集排序，将排序后的节点存储到变量中，然后选择前十个成员。
You might prefer to sort the original node-set, store the sorted nodes in a variable, and select the first ten members of the sorted set.
让我们来看一个在 4 个节点的集群上执行程序的例子，每个节点的内存中都有一个整数，程序的目的是对这 4 个整数求和。
Let's say a program is executing in a cluster with four nodes, each node has an integer in its memory, and the aim is to add these four numbers.
以下配置为运行在ApplicationServerND集群之下的每个BusinessEvent节点建立了一个实例，附带为集群的每个节点建立一对被动机。
The following configuration sets up a machine for each node in the Business Event nodes running under an Application Server ND cluster, along with a single passive machine.
Compute节点上的多个新输出终端均可帮助简化流，并能消除对Filter或RouteToLabel节点的需求。
The new multiple out terminals on the Compute node all the flow to be simplified and eliminated the need for either Filter or RouteToLabel nodes.
JMS传输节点提供了不同级别的事务支持，可以将事务支持作为节点实例的属性，按照您的特定需求对其进行配置
The JMS transport nodes offer different levels of transactional support, which can be configured as a property of the node instance depending on your particular requirements
图14对比了在启用和禁用绑定的情况下netserver可伸缩性测试的结果，测试使用2个适配器(前2个节点上各使用一个适配器)和4个适配器(所有4个节点上各使用一个适配器)。
Figure 14 shows a comparison of the netserver scalability tests when using 2 adapters (1 on each of the first 2 nodes) and 4 adapters (1 on each of all 4 nodes) with and without bonding.
这些信息表示相关的运作节点对主题系统的请求，或系统向一个或多个那样的节点的请求。
These messages represent requests made to the subject system by associated operational nodes, or requests made by the system to one or more of those nodes.
这样一来，一个节点可以计算一个块的散列值；将较小的签名转移到对等节点，该节点也可以计算散列值，然后对两者进行比较。
In this way, a node computes a hash of a block; transfers the much smaller signature to the peer node, which also calculates the hash; and then compares them.
而且，对会话的每次变化都会形成对每个节点的操作，因为节点必须处理进来的消息更新，让会话的备份拷贝与变化一致。
Furthermore, every change to any session also creates work for every node, because it has to process an incoming update message and make its backup copy of the session consistent with the changes.
在这里要注意一点，不管子节点有何标记，对所有的子节点都进行迭代。
A point to note is that iteration takes place over all child nodes, whatever tags they may have.
问题在于将内联标记作为子元素处理，技术上讲这样是对的，但这样却使您不能决定PC DATA节点和子元素节点之间的关系了。
The problem is that inline markup is treated as a child element, which is technically true, but it does not let you determine the relations between PCDATA nodes and child element nodes.
对计算节点的供应采用的是无磁盘的方法，计算节点从管理节点引导。
The diskless method of provisioning the compute nodes is used, whereby the nodes boot from the management node.
每一个节点上显示的数字都是优化器对基础数据源或操作节点的基数的估计。
The number shown in each node is the optimizer's estimate for the cardinality of the underlying data source or operation node.
默认情况下，在模板实现期间，所有节点都被实现为主节点，这种节点支持对复制的随处更新。
By default, all nodes in the template realization are realized as primary nodes that support update anywhere replication.
更糟糕的是，级联删除不存在，因此如果我使用相同的技术来建模一个“一对多”关系并删除父节点，那么我得到一些无效的子节点。
Worse, cascading deletes don't exist, so if I used the same technique to model a one-to-many relationships, and the parent were removed, I could end up with stale children.
实际上，绑定标识出一个或一组节点，然后对这些节点施加特定的限制，进而帮助定义节点的行为。
Rather, a binding identifies a node or a set of nodes, then places specific restrictions on those nodes, which in turn help to define the node's behavior.
由于每个节点都只能访问自己的内存，如果其他节点需要访问这些内存中的数据，就必须对这些数据结构进行复制并通过网络进行传送，这会导致大量的网络负载。
Because each node has access to only its own memory, data structures must be duplicated and sent over the network if other nodes want to access them, leading to network overhead.
在本示例中，我们将禁用所有的非叶节点，因为通常非叶节点只用来对希望对其执行任务的那些项进行分类。
In this example, we will disable all non-leaf nodes, because it is common that non-leaf nodes are just used for categorizing the items that you want to perform tasks on.
由于停止节点对整个节点具有全局效果，在有几个分支并列执行的流程模型中，我们在放置停止节点时必须十分小心。
Given the more global effect of the stop node on the entire process, we have to be careful putting a stop node in process models that can have several branches executing in parallel.
包含多条平行线路的一对分离/连接节点可能出现在另一对分离/连接节点的一条平行线路上。
A pair of split and join nodes encompassing multiple parallel routes can reside on a parallel route in the scope of another pair of split and join nodes.
它接受一个XML文档作为输入，返回一系列节点或对一系列节点应用函数的结果。
It takes an XML document as input and returns a sequence of nodes or the result of applying a function to a sequence of nodes.
一个更有意思的区别是出现了一对中间节点，N1和N2，以及输出节点数量从两个变成了四个(O1到O4)。
A more interesting difference is a pair of intermediary nodes, N1 and N2, and an increase in the number of output nodes from two to four, O1-O4.
对要加入集群中的所有其他节点，例如计算节点、用户节点和管理节点，请在以后步骤中添加类似于_s： client -nonquorum的项。
Use entries similar to _s: client-nonquorum in later stages for all the other nodes to be added to the cluster, such as compute nodes, user nodes, and management nodes.
我们向您展示了DOMLevel3Core是如何使得对节点的处理更加容易的，不管这种处理是重命名节点，将节点从一个文档移到另一个文档，还是比较节点。
We've shown you how DOM Level 3 Core can make your life easier when working with nodes, whether it is renaming a node, moving nodes from one document to another, or comparing them.
PROCESS_SKIP——访问程序对该节点的子节点不感兴趣，所以accept返回true。
PROCESS_SKIP — the visitor isn't interested in the node's children, so accept returns true.
应用推荐