This node is shown in Figure 1.
节点如图1所示。
This node has two service interfaces
该节点具有两个服务接口
Initiate verify and sync from this node.
从这个节点启动检查和同步。
Yeah. And what does this node look like?
太好了，那这个节点应该是怎样的呢？
And what is this node going to look like?
这个节点应该是什么样子呢？
And we ask, what do we get with this node?
然后我们问，这个节点我们获得的是什么？
This node contains the unparsed XML chunk.
该节点包含未解析的XML 块。
This node type represents JCRWiki entries.
这个节点类型表示 JCRWiki 的条目。
This node doesn't have to be a master node.
这个节点不必是主节点。
There are two approaches to using this node.
可采用两种方法使用此节点。
This node can be called as principal secondary.
该节点可称为主要辅助节点。
Next, any extended data is applied to this node object.
接下来，将任何扩展数据应用于这个节点对象。
This node is physically located away from the main cluster.
此节点的物理位置与主集群不在一起。
Last, insert this node into the cluster: tyd -m 192.168.1.10.
最后，将这个节点加入到集群之中：tyd- m 192.168.1.10。
Drupal then checks if comments should be rendered for this node.
然后，Drupal检查是否应该为这个节点显示评论。
Last, announce this node as the master node in the cluster: tyd.
最后，声明这个节点是集群中的主节点：tyd。
Hence this node extends the capabilities offered via a Route node.
因此，该节点扩展了Route节点提供的功能。
Next provide a name for this node; for example purposes, call it CNS.
接下来，要为该节点提供一个名称，例如cns。
A property of this node is its unique identifier — a 1 to 12 character label.
此结点有一个属性，即它的唯一标识符——由1到12个字符组成的标签。
This node type represents images and other binary content in a JCRWiki entry.
这个节点类型表示JCRWiki条目中的图片和其他二进制内容。
You also need to provide a name for this node; for example purposes, call it CNS.
您还需要为该节点提供一个名称；例如，称之为cns。
The sub-problem is this: "Is the search string the same as the one in this node?"
子问题是这样：“搜索字符串是否与这个节点中的字符串相同？”
This node USES XPath exclusively for its message processing transformation language.
该节点只使用XPath作为其消息处理转换语言。
This node can lookup a collection of named column values from a located database row.
该节点可以从特定的数据库行查找指定列值的集合。
If you return false from the visit method, the children of this node won't be visited.
如果visit方法返回false，那么该节点的子接点将不会被访问。
In the current setup, this node is the active one and owns the resources of the cluster.
在当前的设置中，这个节点是主动节点，并拥有集群的资源。
This node is connected to Task 1, symbolized by a yellow rectangle with rounded corners.
此节点连接到Task1，后者用黄色的圆角矩形表示。
On the right panel, the data types that contribute significantly to this node are listed.
在右面板中，列出了显著占用此节点的数据类型。
This identifier must be globally unique within the broker instance that this node is deployed.
此标识符必须在此节点部署到的代理实例内具有全局唯一性。
In the current setup, this node is the passive node and ACTS like a standby node for the cluster.
在当前的设置中，这个节点是被动节点，它作为集群的备用节点。
应用推荐