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?
然后我们问，这个节点我们获得的是什么？
There are two approaches to using this node.
可采用两种方法使用此节点。
Next, any extended data is applied to this node object.
接下来，将任何扩展数据应用于这个节点对象。
Drupal then checks if comments should be rendered for this node.
然后，Drupal检查是否应该为这个节点显示评论。
Hence this node extends the capabilities offered via a Route node.
因此，该节点扩展了Route节点提供的功能。
A property of this node is its unique identifier — a 1 to 12 character label.
此结点有一个属性，即它的唯一标识符——由1到12个字符组成的标签。
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?"
子问题是这样：“搜索字符串是否与这个节点中的字符串相同？”
In the current setup, this node is the active one and owns the resources of the cluster.
在当前的设置中，这个节点是主动节点，并拥有集群的资源。
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.
在当前的设置中，这个节点是被动节点，它作为集群的备用节点。
The properties pane of this node reveals the time spent in the actual node and the total elapsed time.
该节点的属性窗格显示在实际节点上花费的时间和总运行时间。
If these conditions are met, Drupal starts to assemble a form required to add a node of this node type.
如果这些条件都得到满足，Drupal就开始组装添加这种类型的节点所需的表单。
This handler first pegs the escalation counter and then completes a task instance, associated with this node.
这个处理器首先记录上报计数器，接着完成此节点关联的任务实例。
Before any rendering of the node can proceed, a container for all the data associated with this node is created.
在处理任何节点的显示之前，要为与这个节点相关联的所有数据创建一个容器。
It checks one of the ASTVisitor's Boolean fields to determine if the visitor is interested in visiting this node.
检查ASTVisitor的Boolean字段中的一个，来确定访问器是否对访问此节点感兴趣。
Passing: jump indicates that iteration should jump to the next node and skip all remaining visitors for this node.
传递：jump表示迭代应跳转到下一个节点，并跳过此节点的所有剩余访问者。
To set up this node as a backup, you need to automatically replicate the deployment manager's cell-wide configuration.
要将此节点设置为备份，您需要自动复制部署管理器的计算单元范围的配置。
This node is added to the beginning of the lookup list and a reference to this node is returned as the import context.
把这个节点添加到查找列表的开头，作为导入上下文返回节点的引用。
The starting point is a root node (the root node is the base of the tree; all other nodes are descendents of this node).
起始点是一个rootnode (根节点是树的根基，所有其他节点都是这个节点的后代)。
The deployment manager USES this node information to determine which administrative functions are actually valid for a given node.
部署管理器利用节点信息来确定对于特定节点，那些管理功能是真正有效的。
Through this node such data retrieval capabilities can be achieved without the need for expert messaging or SQL programming knowledge.
有了该节点，即使没有专业的消息传递或SQL编程知识，也可以实现这种数据检索功能。
When the initial control message is sent to this node, the "TimeoutNotify_BURST" node will create timer events at the specified intervals.
将初始控制消息发送到此节点时，“TimeoutNotify_BURST”节点将按照指定的时间间隔创建计时器事件。
Using the example of "bosapora01" as depicted in Table 4, this node name would also be used as a host name with an IP address assigned to it.
以表4中的“bosapora01”节点为例，这个节点名也用作主机名，与分配给节点的一个IP地址相关联。
If the Multiple rows option is selected for this node, then for each row in the result set the entries in the Data elements table are executed.
如果选择了该节点的Multiplerows选项，那么对于结果集中每一行，都将执行Data元素中的条目。
Finally, if the tree node is ConnectionFactoryInfo, the children of this node will be connection properties defined for the corresponding connection factory.
最后，如果树节点是ConnectionFactoryInfo，那么该节点的子节点将是为相应的连接工厂定义的连接属性。
The visual actions that occur are that a style is applied to indicate the node has been removed (red strikethrough), and the undo menu item is now enabled for this node.
其显示效果是应用了一个样式来表明此节点已经删除(红色的删除线)，而undo菜单项现在对此节点是启用的。
应用推荐